slide1
Download
Skip this Video
Download Presentation
Documentation (Changes, Inspections)

Loading in 2 Seconds...

play fullscreen
1 / 10

Documentation (Changes, Inspections) - PowerPoint PPT Presentation


  • 66 Views
  • Uploaded on

Documentation (Changes, Inspections). Project Changes (pg 16). Page numbers refer to May 2013 User’s Guide. “Change happens” After Project Notification Change Form is needed when: In-water work variance (AKA IWWE)

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Documentation (Changes, Inspections)' - salaam


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
slide1

Documentation

(Changes, Inspections)

slide2

Project Changes (pg 16)

Page numbers refer to

May 2013 User’s Guide

  • “Change happens”
  • After Project Notification
  • Change Form is needed when:
    • In-water work variance (AKA IWWE)
    • Project changes that substantively impact species differently than per Notification
      • cannot meet SW management on-site, fluvial performance standards, fish passage, etc.
    • Alternative mitigation
  • Project Change form versus Project Completion Report
  • Submittal process like Notification
slide4

Why is the change necessary?

  • If IWWE, also describe measures already conducted to try to avoid a variance.
  • Habitat features/resources impacted specific to each activity to be changed.
  • Is change with in scope of FAHP or other pertinent regulatory standards (if not, would it trigger ESA re-initiation)?
slide6

Signature blocks to be like Notification

  • Section to be revised…Attachments for Regulatory Approvals
  • NMFS, DSL will want to see ODFW approval (attach email communication)
  • USACE may want to see NMFS, USFWS, or ODFW approval
  • Processing/transmittal:
  • If FAHP Project change, process/transmit as per Notification, after obtaining ODFW approval
  • Other regulatory project changes, check with regulators
  • Maintain final/signed in FAHP Project’s FTP folder
environmental inspections pgs 7 13
Environmental Inspections(pgs 7, 13)
  • Who, When? (see Roles module)
  • As relevant to document “may affect” work
    • Clearing in rip. zone – avoidance areas, native materials salvage
    • Herbicide treatment – OK chemicals, buffers maintained?
    • In-water work or work near species/habitat, bubble curtains
    • Habitat improvements, site restoration
  • Transmittal is different than Notification
    • No need for signatures
    • Upload to Project’s FTP folder
    • E-mail notice to FAHP Project Stakeholders
fish salvage report pg 14
Fish Salvage Report (pg 14)
  • ODFW form
    • see ODOT biology website, “forms”
  • Due 30 days after salvage
  • FAHP transmittal like Inspection
    • also e-mail to ODFW, NRU-Trans

Must call NMFS

for sick, injured

or dead ESA fish

ad