ODFW Fish Passage Plan Notification Sample Clauses

ODFW Fish Passage Plan Notification. The proposed plan to remove the pedestrian bridge will require approval from ODFW in compliance with the State Fish Passage Plan for abandonment of in-water structures, per ORS 509. The proposed project will require plans detailing removal of the bridge structure, piers, and abutments above and below grade, including removal of bank revetment or riprap installed during construction or maintenance of the bridge, and regrading banks to match the adjacent grade. Consultant shall coordinate with ODFW to for the submittal of plans and documentation required to obtain ODFW approval for the proposed removal of the bridge structure under the ODFW Fish Passage Plan requirements.
AutoNDA by SimpleDocs

Related to ODFW Fish Passage Plan Notification

  • Employee Notification A copy of any disciplinary action or material related to employee performance which is placed in the personnel file shall be provided to the employee (the employee so noting receipt, or the supervisor noting employee refusal to acknowledge receipt) or sent by certified mail (return receipt requested) to the employee's last address appearing on the Employer's records.

  • Control Area Notification At least three months before Initial Synchronization Date, Interconnection Customer shall notify Distribution Provider in writing of the Control Area in which the Generating Facility will be located. If Interconnection Customer elects to locate the Generating Facility in a Control Area other than the Control Area in which the Generating Facility is physically located, and if permitted to do so by the relevant transmission tariffs, all necessary arrangements, including but not limited to those set forth in Article 7 and Article 8 of this GIA, and remote Control Area generator interchange agreements, if applicable, and the appropriate measures under such agreements, shall be executed and implemented prior to the placement of the Generating Facility in the other Control 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.

  • Balancing Authority Area Notification At least three months before Initial Synchronization Date, the Interconnection Customer shall notify the CAISO and Participating TO in writing of the Balancing Authority Area in which the Large Generating Facility intends to be located. If the Interconnection Customer intends to locate the Large Generating Facility in a Balancing Authority Area other than the Balancing Authority Area within whose electrically metered boundaries the Large Generating Facility is located, and if permitted to do so by the relevant transmission tariffs, all necessary arrangements, including but not limited to those set forth in Article 7 and Article 8 of this LGIA, and remote Balancing Authority Area generator interchange agreements, if applicable, and the appropriate measures under such agreements, shall be executed and implemented prior to the placement of the Large Generating Facility in the other Balancing Authority Area.

  • Collocation Transfer of Responsibility Without Working Circuits The Collocation is not serving any End User Customers and does not have active service terminations (e.g., Interconnection trunks or UNE Loops) or 2) Collocation Transfer of Responsibility With Working Circuits – The Collocation has active service terminations, such as Interconnection trunks or is serving End User Customers.

  • Unbundled Network Terminating Wire (UNTW) 2.8.3.1 UNTW is unshielded twisted copper wiring that is used to extend circuits from an intra-building network cable terminal or from a building entrance terminal to an individual End User’s point of demarcation. It is the final portion of the Loop that in multi-subscriber configurations represents the point at which the network branches out to serve individual subscribers.

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

  • Benefit Level Two Health Care Network Determination Issues regarding the health care networks for the 2017 insurance year shall be negotiated in accordance with the following procedures:

  • Unauthorized Access Notification LEA shall notify Provider promptly of any known or suspected unauthorized access. LEA will assist Provider in any efforts by Provider to investigate and respond to any unauthorized access.

  • Sick Leave Notification Employees must contact their supervisor or assistant manager one (1) hour prior to the start of their assigned shift at the designated contact number to be placed on the sick board. Employees wishing to return to work must notify their supervisor or assistant manager before 4:00pm of the day before desiring to return to work.

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