Effectiveness Monitoring Conditions Sample Clauses

Effectiveness Monitoring Conditions. 641 The effectiveness monitoring conditions will be influenced by the complexity of 642 the safe harbour instruments and the type of instrument used. Please refer to 643 section 4.5 of the Endangered Species Act Submission Standards For Activity 644 Review and 17 (2)(c) Overall Benefit Permits (OMNR, 2012) for guidance on 645 effectiveness monitoring in the context of safe harbour instruments issued 646 through overall benefit permits. 647 In order to further facilitate the implementation of safe harbour instruments in the 648 context of stewardship agreements, protection or recovery permits or overall 649 benefit permits, the conditions of an effectiveness monitoring plan should be 650 simple and reasonable for any proponent to implement. The information collected 651 for effectiveness monitoring should be based on criteria relevant to the species 652 covered by the instrument and be scaled relative to the complexity of the project. 653 The information collected within an effectiveness monitoring program should 654 include, but is not limited to: 655  Species descriptions: 656 o A list and number of individuals of each species at risk within the 657 safe harbour habitat as well as their sex and age class, if known; 658 o The date and times of species at risk observations; and 659 o General behavioral patterns of species at risk in the safe harbour 660 habitat. 661  Habitat descriptions: 662 o Size, composition and characteristics of the safe harbour habitat; 663 and 664 o Additional descriptive information pertaining to the safe harbour 665 habitat. 666  Management actions taken to xxxxxx productivity of the safe harbour 667 habitat.
Sample 1
AutoNDA by SimpleDocs

Related to Effectiveness Monitoring Conditions

  • Effectiveness of Agreement This Agreement shall become effective upon the execution and delivery hereof by the parties hereto.

  • Effectiveness of Contract This Contract shall come into effect on the date the Contract is signed by both parties or such other later date as maybe stated in the SCC.

  • Conditions to Effectiveness This Amendment shall become effective as of the date hereof and upon the satisfaction of the following conditions precedent:

  • EFFECTIVENESS; TERMINATION 5.01. The Additional Conditions of Effectiveness consist of the following:

  • 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.

  • 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:

  • 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.

  • Initial Forecasts/Trunking Requirements Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom CSTC decides to market its services, Verizon will be largely dependent on CSTC to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to CSTC as CSTC provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when CSTC expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks CSTC suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to CSTC is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and CSTC’s previous forecasts have proven to be reliable and accurate.

  • PROJECT CONDITIONS A. The Grantee agrees to the following Project Conditions:

  • Supported Initial and Renewal Registration Periods a. Initial registrations of Registered Names (where available according to functional specifications and other requirements) may be made in the registry for terms of up to ten years.

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