1 / 15

Documentation (Initiation, Notification)

Documentation (Initiation, Notification). See pg 5 May 2013 User’s Guide. Early Coordination and Initiation. It’s a process , not just a form Starts after Project Kick-off Coordinate with Services (e.g., NMFS liaison) Develop FAHP Project Stakeholders list (pg 8)

karif
Download Presentation

Documentation (Initiation, Notification)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Documentation (Initiation, Notification)

  2. See pg 5 May 2013 User’s Guide

  3. Early Coordination and Initiation • It’s a process, not just a form • Starts after Project Kick-off • Coordinate with Services (e.g., NMFS liaison) • Develop FAHP Project Stakeholders list (pg 8) • Create Project’s FTP folder • Documentation (Required for Project Notification) • Project Initiation form, Initiation memo, or e-mail • Upload to FTP folder, e-mail notification to stakeholders

  4. Current forms available on FAHP Website

  5. Activities Not Requiring Services Approval(pg 12) • Meet in-water work period(s) • Bridge replacement that meets fluvial performance and pile driving hydroacoustic standards (pgs 25,36) • No stream channel or waterway enhancements, or meet standards (pg 28) • Stormwater flow management in drainage basins larger that 100 mi2 & meets standards (pg 18) • None or only minor modifications to buffer distances, riparian habitat impacts • minor modifications must be described in the Project Notification, including justification for lack of adverse impacts

  6. Activities Requiring Services Approval(pg 12) • Actions with required mitigation (pg 17) • In-water work variance • Fisheries restoration • Blasting in/near aquatic habitats (NLAA only) • Bridge replacement cannot meet fluvial performance or pile driving hydroacoustic standards (pgs 25,36) • Stream channel or waterway enhancements does not meet standards (pg 28) • Flow management drainage basins < 100 mi2 • Other modifications to FAHP design standards with direct impacts to Covered Species

  7. Project Notification • Likewise, is a process, not just a form • Timing based on FHWA requirements for NEPA approval (e.g., CE Close-out Report) • Begin Notification process about 12-weeks prior to deadline for NEPA approval • Local agency should get REU review before this • “Easy” projects may take less time, complex projects or if new to the FAHP may need more • FHWA review 2-4 weeks • NMFS review likely 2-8 weeks • Range depends on complexity and allows for requests for additional information

  8. Project Notification (process) • Quality Control • Check completeness & math; check consistency; Attachments • Check latest Summary of Take (FAHP website) • Upload to Project’s FTP folder • REU transmits Notification to FHWA • See Append. 5 for E-mail content • Must reference early coordination • All require review/approval by FHWA • Routing signatures • File naming

More Related