Show new navigation
On
Columbia Basin Fish and Wildlife Program Columbia Basin Fish and Wildlife Program
Select a work element:
Contract Number:
Contract Title:
200725200 EXP MULTI-SCALE HYPORHEIC ASSESSMENT
Contract Start Date:
10/1/2007
Contract End Date:
1/15/2009
Title:
F: 132 - Submit Annual Report for the period 10/2007 to 9/2008
Description:
Annual progress report that includes details of accomplishments for each work element in the contract: Were the deliverables produced, and, if not, why not? When published and posted on the BPA website - succinctly documents contract performance for the public record. Focus for this contract will be on the technical aspects and accomplishments related to the topic area.
WE Agreement Type:
Contracted
Deliverable Specification:
Upload annual report for the period 1/2007 to 9/2007. Currently, this is done via the BPA website; down the road, this may be done via attachments supported directly within Pisces. For guidance on how/where to upload: https://efw.bpa.gov/Integrated_Fish_and_Wildlife Program/technicalreports.aspx
WSE Effective Budget:
$17,890
% of Total WSE Effective Budget:
21.30%
WSE Start:
08/29/2008
WSE End:
01/15/2009
WSE Completion:
01/12/2009
WSE Progress:
Concluded
WSE ID Continued From:
[Unassigned]
WSE ID Continued To:
[Unassigned]
Finite or Recurring:
Finite

SOWRevision Planned Updated Contractor Comments (optional) BPA Comments (optional)
1. Amendment 003 (10/01/2007 - 09/30/2008) $17,890 $17,890
Work Element Budget (Current Performance Period) $17,890 $17,890

7 Milestones
Sort Type Title Start End Status Modified By Modified Date
A NonT1 Review annual report format requirements 8/29/2008 1/7/2009 Concluded Scott O'Daniel 11/6/2008 3:46:44 PM
Description: Contractor must review formatting requirements before starting the first draft of their report. Please follow the BPA-required format. https://efw.bpa.gov/Integrated_Fish_and_Wildlife_Program/technicalreports.aspx Additionally, I anticipate submitting versions of the final report to J. P. for comments.
B NonT3 Submit report for internal contractor review 8/29/2008 1/9/2009 Concluded Scott O'Daniel 11/6/2008 3:46:44 PM
Description: Use this milestone if the annual report requires an internal review before being reviewed externally. Make sure to allow for both technical and policy reviews if necessary.
C EDRTCFR Email draft of report to COTR for review 8/29/2008 1/9/2009 Concluded Scott O'Daniel 11/6/2008 3:46:44 PM
Description: The draft annual report must be submitted to the BPA COTR in Microsoft Word format (any version of Word is fine).
D RCRC Receive COTR review comments 9/10/2008 1/13/2009 Concluded Scott O'Daniel 11/6/2008 3:46:45 PM
Description: The BPA COTR should provide review feedback and comments within 30 days of receiving the draft annual report. This milestone should therefore have a duration of 30 days.
E FAR Finalize Annual Report 9/17/2008 1/14/2009 Concluded Scott O'Daniel 11/6/2008 3:46:45 PM
Description: Integrate review feedback and comments, and obtain internal signatures if necessary. Convert the annual report to Adobe Acrobat PDF format.
F DELIV Confirm BPA has posted the report 9/25/2008 1/15/2009 Concluded Scott O'Daniel 11/6/2008 3:46:45 PM
Description: It usually takes BPA no more than 30 days to get the report posted. This milestone should therefore have a duration of 30 days. To confirm posting of the report, search the BPA Publications database. https://efw.bpa.gov/Integrated_Fish_and_Wildlife_Program/technicalreports.aspx
G DELIV Final report uploaded to the BPA website 1/15/2009 Concluded Scott O'Daniel 11/6/2008 3:46:45 PM
Description: Upload annual report for the period 1/2007 to 9/2007. Currently, this is done via the BPA website; down the road, this may be done via attachments supported directly within Pisces. For guidance on how/where to upload: https://efw.bpa.gov/Integrated_Fish_and_Wildlife Program/technicalreports.aspx

Implementation Metrics
None

This work element does not require Focal Species
This work element does not require Environmental Compliance
This work element does not require RM&E metadata