Contact Roy Beaty (503) 230-5213

This work element covers written reports of results that typically are submitted to BPA at the end of a contract period for dissemination to the public. Previously called "Annual" reports, these progress reports may cover less than a year or multiple years. They are not required or appropriate for all contracts in all years, but are particularly important when useful results are not captured by standard Pisces metrics or status reports. Progress Reports come in two types. "Technical" reports are used for contracts that develop RM&E Methods and Designs (WE# 156), Analyze/Interpret Data (WE#1 56), and/or CollectGenerate/Validate substantial amounts of data (WE# 157) when it is important also to report the data collection methods. Technical progress reports often use a scientific format, especially when it is important to describe the methods that produced the results. An alternative, less common format could follow the flow of activities described in the contract's statement of work (SOW-based format). After being uploaded to Pisces, Technical reports will be published as Department of Energy Technical Reports, per standard practice. "Non-technical" progress reports also will be uploaded to Pisces, which will provide public access, but will not be "published" as a DoE Technical Report. Non-technical reports may use a range of formats, typically based on the SOW activities, but potentially free-form. They may be mostly photos, simple summaries of data, or a brief description of lessons learned. The most important considerations are that they document completion of the contract's work and capture important information that would not be readily available through other means (e.g., Pisces metrics and status reports).

• Technical (or non-technical) progress report for [previous contract period] in scientific format uploaded to Pisces per on-line specifications.
• Data summary and lessons learned for draft non-technical progress report for [present contract period], which will be submitted during the next contract period.
• Before/after photos, HIP-BO-required reporting information, and site inspection reports (appendix) for road obliteration activities, uploaded to Pisces as non-technical reports.

Rules and Examples (work element scenarios and associated rules)

Rule 1: Use a separate WE for each progress report being worked on during the contract period, and clearly identify the different reports in the WE titles.

Rule 2: If previous progress reports have been deficient, invest extra effort in describing the contents of this progress report in the Deliverable Specification.

Rule 3: Do not include activities that have their own WEs, such as data analysis.

Rule 4: Do not include COTR review of the draft report prior to uploading.

• Review progress report format requirements
Contractor must review formatting requirements before starting the first draft of their report. Please follow the BPA-required format. http://www.efw.bpa.gov/IntegratedFWP/technicalreports.aspx
• Submit progress report for internal contractor review
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.
• Submit progress report for external review
Use this milestone if the progress report requires external review.
• Attach Progress Report in Pisces Deliverable
Use the attachment tab in Pisces to attach your progress report. Progress reports attached in Pisces will be posted on the web.
• Confirm BPA has posted the progress report
It usually takes BPA 30-45 days to post the final version of a report. This milestone's end date should therefore be 45 days after the Deliverable milestone. You will receive an email from BPA confirming that your report has been finalized and posted to the web.
• Internal agency/tribal review of draft
• Submit draft for technical/co-manager review (if necessary, and considering time/costs)
• Revisions in response to review of draft
• Finalize report
• Upload report in Pisces

Metrics

Location Guidance

No location needed for this work element.

Applicability and status of the following environmental compliance requirements can be found on the Environmental Compliance tab for that work element in your SOW for all 2007 contracts forward. BPA's Environmental staff will update and maintain this information in Pisces in real time, so that you can check the status of environmental compliance on your project at any time.

Note: Many of the fields are set to auto-load in Pisces, but the settings will be reviewed by BPA's Environmental staff prior to the contract being finalized, and may be revised depending on the specific circumstances.

National Environmental Policy Act (NEPA)

NEPA coverage for this work element will be identified by BPA's Environmental Compliance Lead.

Endangered Species Act (ESA)

ESA consultation is typically not required for this work element.

National Historic Preservation Act (NHPA)

NHPA Section 106 consultation is typically not required for this work element.

Public Involvement

Public involvement is typically not required for this work element.

• WE# 183, Produce Journal Article
• WE# 185, Produce Pisces Status Report
• WE# 165, Produce Environmental Compliance Documentation