Level of Specificity Sample Clauses

Level of Specificity. The level of planning for the Oregon Fish and Wildlife Commission decision will of necessity be limited to a description of the Fish Species for reintroduction, the geographical extent of those Species, identification of critical uncertainties to be addressed during reintroduction, broad strategies for reintroduction (i.e. active movement versus. volitional re-colonization), and a conceptual plan for future management once anadromous Fish Species are thriving in the Upper Klamath Basin (Phase II Reintroduction).
AutoNDA by SimpleDocs

Related to Level of Specificity

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones: 6.1 Substantial Site work completed. On or before December 31, 2020 Interconnection Customer must demonstrate completion of at least 20% of project site construction. At this time, Interconnection Customer must submit to Interconnected Transmission Owner and Transmission Provider initial drawings, certified by a professional engineer, of the Customer Interconnection Facilities. 6.2 Delivery of major electrical equipment. On or before December 31, 2021, Interconnection Customer must demonstrate that all generating units have been delivered to Interconnection Customer’s project site.

  • Quality Specifications SANMINA-SCI shall comply with the quality specifications set forth in its Quality Manual, incorporated by reference herein, a copy of which is available from SANMINA-SCI upon request.

  • Reasonable Suspicion Testing All Employees Performing Safety-Sensitive Functions A. Reasonable suspicion testing for alcohol or controlled substances may be directed by the Employer for any employee performing safety-sensitive functions when there is reason to suspect that alcohol or controlled substance use may be adversely affecting the employee’s job performance or that the employee may present a danger to the physical safety of the employee or another. B. Specific objective grounds must be stated in writing that support the reasonable suspicion. Examples of specific objective grounds include but are not limited to: 1. Physical symptoms consistent with alcohol and/or controlled substance use; 2. Evidence or observation of alcohol or controlled substance use, possession, sale, or delivery; or 3. The occurrence of an accident(s) where a trained manager, supervisor or lead worker suspects alcohol or other controlled substance use may have been a factor.

  • Notice of Special Matters The Corporation covenants with the Warrant Agent that, so long as any Warrant remains outstanding, it will give notice to the Warrant Agent and to the Registered Warrantholders of its intention to fix a record date that is prior to the Expiry Date for any matter for which an adjustment may be required pursuant to Section 4.1. Such notice shall specify the particulars of such event and the record date for such event, provided that the Corporation shall only be required to specify in the notice such particulars of the event as shall have been fixed and determined on the date on which the notice is given. The notice shall be given in each case not less than 14 days prior to such applicable record date. If notice has been given and the adjustment is not then determinable, the Corporation shall promptly, after the adjustment is determinable, file with the Warrant Agent a computation of the adjustment and give notice to the Registered Warrantholders of such adjustment computation.

  • Core Profession Specific Develop and administer procedures to support effective and efficient National Board and committee operations Profession-specific services, as listed in the National Board’s regulatory plan and annual budget.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Registry Performance Specifications Registry Performance Specifications for operation of the TLD will be as set forth in Specification 10 attached hereto (“Specification 10”). Registry Operator shall comply with such Performance Specifications and, for a period of at least one (1) year, shall keep technical and operational records sufficient to evidence compliance with such specifications for each calendar year during the Term.

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