Development In Focal Areas and Connectivity Zones Where Impacts Exceed Habitat Goals Sample Clauses

Development In Focal Areas and Connectivity Zones Where Impacts Exceed Habitat Goals. The habitat goals for focal areas and connectivity zones are no more than 30% development impacts in focal areas and 60% in connectivity zones. Where those development goals are surpassed for an individual reporting unit, as identified in Appendices D and E of the RWP (pgs. 80–83, 179–182), the habitat goals under the plan cannot be met. In that case, remediation of existing impacts will be required for further development. A portion of the necessary offset units must be acquired by remediation of existing impacts in proportion to the amount of newly impacted acreage exceeding the stated goals. For example, if 20% of the newly impacted acreage associated with a development were in excess of the impact goal for a reporting unit that proportion of the resulting offset units must be of the remediation variety. The remediation offset units should be generated from the same reporting unit as the new impact, but if that is not possible they can originate from a nearby reporting unit within the same ecoregion.
AutoNDA by SimpleDocs

Related to Development In Focal Areas and Connectivity Zones Where Impacts Exceed Habitat Goals

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • ROAD DIMENSIONS Purchaser shall perform road work in accordance with the dimensions shown on the TYPICAL SECTION SHEET and the specifications within this road plan.

  • For Product Development Projects and Project Demonstrations  Published documents, including date, title, and periodical name.  Estimated or actual energy and cost savings, and estimated statewide energy savings once market potential has been realized. Identify all assumptions used in the estimates.  Greenhouse gas and criteria emissions reductions.  Other non-energy benefits such as reliability, public safety, lower operational cost, environmental improvement, indoor environmental quality, and societal benefits.  Data on potential job creation, market potential, economic development, and increased state revenue as a result of the project.  A discussion of project product downloads from websites, and publications in technical journals.  A comparison of project expectations and performance. Discuss whether the goals and objectives of the Agreement have been met and what improvements are needed, if any.

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK Firms and/or individuals that assisted in the development or drafting of the specifications, requirements, statements of work, or solicitation documents contained herein are excluded from competing for this solicitation. This shall not be applicable to firms and/or individuals providing responses to a publicly posted Request for Information (RFI) associated with a solicitation.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least thirty (30) days written notice to the SLDC and GUVNL, of the date on which it intends to synchronize the Power Project to the Grid System.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Teaching Staff Assigned to More Than One Building Each Educator who is assigned to more than one building will be evaluated by the appropriate administrator where the individual is assigned most of the time. The principal of each building in which the Educator serves must review and sign the evaluation, and may add written comments. In cases where there is no predominate assignment, the superintendent will determine who the primary evaluator will be.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • AIN Selective Carrier Routing for Operator Services, Directory Assistance and Repair Centers 4.3.1 BellSouth will provide AIN Selective Carrier Routing at the request of <<customer_name>>. AIN Selective Carrier Routing will provide <<customer_name>> with the capability of routing operator calls, 0+ and 0- and 0+ NPA (LNPA) 555-1212 directory assistance, 1+411 directory assistance and 611 repair center calls to pre-selected destinations.

  • Synchronisation Commissioning and Commercial Operation 8.1 The Developer shall provide at least forty (40) days advanced preliminary written notice and at least twenty (20) days advanced final written notice to ESCOM of the date on which it intends to synchronize the Power Project to the Grid System.

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