Nutrient Joint Priority [new] Sample Clauses

Nutrient Joint Priority [new]. Reduction of nutrients in Illinois, from both point sources and non-point sources, remains a high priority for both Region 5 and Illinois EPA. Region 5 urges development of nutrient TMDLs and adoption of nutrient criteria by Illinois and therefore, Region 5 would like to work jointly with Illinois EPA over the next year to identify and implement critical next steps that will maxi xxxx the likelihood of developing numeric nutrient criteria that can be adopted by Illinois and use a science-based approach to develop TMDL targets for several nutrient impaired watersheds. In recognition of the keen interest of both agencies, Region 5 and Illinois EPA will work together to:
AutoNDA by SimpleDocs

Related to Nutrient Joint Priority [new]

  • Telephone Service Prioritization; 4.1.4.11.2 Related services for handicapped;

  • Provisioning of High Frequency Spectrum and Splitter Space 3.2.1 BellSouth will provide <<customer_name>> with access to the High Frequency Spectrum as follows:

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

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

  • Authorization Required Prior to Parallel Operation 2.2.1 The NYISO, in consultation with the Connecting Transmission Owner, shall use Reasonable Efforts to list applicable parallel Operating Requirements in Attachment 5 of this Agreement. Additionally, the NYISO, in consultation with the Connecting Transmission Owner, shall notify the Interconnection Customer of any changes to these requirements as soon as they are known. The NYISO and Connecting Transmission Owner shall make Reasonable Efforts to cooperate with the Interconnection Customer in meeting requirements necessary for the Interconnection Customer to commence parallel operations by the in-service date.

  • Provision of Interconnection Financial Security The Interconnection Customer is obligated to provide all necessary Interconnection Financial Security required under Section 11 of the GIDAP in a manner acceptable under Section 11 of the GIDAP. Failure by the Interconnection Customer to timely satisfy the GIDAP’s requirements for the provision of Interconnection Financial Security shall be deemed a breach of this Agreement and a condition of Default of this Agreement.

  • Programming Phase 2.2.1.2. Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

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

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