Replacement Developer Obligations After Project Entitlement Approval Date Entitlement Acquisition
Replacement Developer Obligations After Project Entitlement Approval Date Entitlement Acquisition Sample Clauses
Related to Replacement Developer Obligations After Project Entitlement Approval Date Entitlement Acquisition
ADDITIONAL SPECIAL CONTRACT CONDITIONS A. Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:
Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.
Project Completion Date It is agreed between the Parties that the Project Completion Date is <END DATE, YEAR>. If the Project is not completed by such date then, subject to an amendment agreed to between the Parties, Alberta Innovates may elect to terminate this Investment Agreement. In such event, Alberta Innovates will notify the Applicant of its decision to terminate as soon as reasonably practical and shall advise the Applicant of the effective date of termination. Alberta Innovates will have no liability or obligation to reimburse the Applicant for any Project Costs incurred after the effective date of termination and may require the Applicant to return any portions of the Investment which were spent on Ineligible Expenses. Additionally, any portion of the Investment not used and accounted for in accordance with this Agreement as of the Project Completion Date or earlier termination is repayable by the Applicant to AI at AI’s request.
Notice to Proceed - Land Acquisition The acquisition of the Land shall not occur until the Director has issued a written Notice to Proceed for land acquisition to the Recipient (the "Notice to Proceed"). Such Notice to Proceed will not be issued until the Director has received a Request to Proceed acceptable to the Director and is assured that the Recipient has complied with all requirements for the approval of a grant under Revised Code Sections 164.20 through 164.27 and any requirements for land acquisition set forth in this Agreement, including without limitation the OPWC's approval of the proposed Deed Restrictions and Title Agent. The Notice to Proceed also shall specify the time frame for the Closing.
Unbundled Loop Modifications (Line Conditioning 2.5.1 Line Conditioning is defined as routine network modification that BellSouth regularly undertakes to provide xDSL services to its own customers. This may include the removal of any device, from a copper Loop or copper Sub-loop that may diminish the capability of the Loop or Sub-loop to deliver high-speed switched wireline telecommunications capability, including xDSL service. Such devices include, but are not limited to, load coils, excessive bridged taps, low pass filters, and range extenders. Excessive bridged taps are bridged taps that serves no network design purpose and that are beyond the limits set according to industry standards and/or the XxxxXxxxx XX 00000.
Unbundled Copper Loop – Non-Designed (UCL-ND 2.4.3.1 The UCL–ND is provisioned as a dedicated 2-wire metallic transmission facility from BellSouth’s Main Distribution Frame (MDF) to a customer’s premises (including the NID). The UCL-ND will be a “dry copper” facility in that it will not have any intervening equipment such as load coils, repeaters, or digital access main lines (DAMLs), and may have up to 6,000 feet of bridged tap between the End User’s premises and the serving wire center. The UCL-ND typically will be 1300 Ohms resistance and in most cases will not exceed 18,000 feet in length, although the UCL-ND will not have a specific length limitation. For Loops less than 18,000 feet and with less than 1300 Ohms resistance, the Loop will provide a voice grade transmission channel suitable for Loop start signaling and the transport of analog voice grade signals. The UCL-ND will not be designed and will not be provisioned with either a DLR or a test point.
Contract Closure Contracting Officer shall give appropriate written notice to Purchaser when Purchaser has complied with the terms of this contract. Purchaser shall be paid refunds due from Timber Sale Account un- der B4.24 and excess cooperative deposits under B4.218.
PROJECT CONDITIONS A. The Grantee agrees to the following Project Conditions:
ENCROACHMENT/ACQUISITION The Assignee/Bank has no notice or knowledge of any encroachment or that the Government or any other authority has any immediate intention of acquiring the whole or any part of the Property for roads or any other improvement schemes and if such encroachment shall be found to exist or if the Government or any local authority has any such intention, the same shall not annul the sale or shall any abatement or compensation be allowed in respect thereof.
Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.
