NFFP71002102783 SOW RFQ.docx

STATEMENT OF NEED FOR SUPPLY OR SERVICE

NF-FP7100-21-02783 CB43021

1.0 GENERAL

1.1 BACKGROUND

Low-tech process-based restoration of rivercapes (http://lowtechpbr.restoration.usu.edu) has emerged as one of the few viable and scalable techniques for improving riverscape health and addressing bottle necks in juvenile and spawning lifestages of endangered salmon populations. A protocol has been developed by Weber et al. (2020) for implementing and monitoring LTPBR, but as the projects begin to get larger in size, a standardized, template and rule-based implementation framework of this workflow is necessary. Ultimately, the workflow should be developed into an electronic data capture platform; however, the initial design and prototyping work must first be undertaken such that subsequent tool development can be most efficiently engineered – that initial work is specified in this purchase request.

1.2 OBJECTIVE

For this scope of work, we seek a technical, repeatable, transparent workflow for facilitating the Low-Tech Process-Based Restoration (LTPBR) design and planning process (http://lowtechpbr.restoration.usu.edu). A standard of practice for LTPBR was established by Wheaton et al. (2019). As a result, 1000s of practitioners have been introduced to the basic theory and rationale. University courses and professional practice certificates are taught using this framework, and numerous state, federal and local action agencies are now implementing this standard of practice. Moreover, federal, state and local regulatory agencies are increasingly recognizing this standard of practice as an effective management proscription in programmatic consultations and protected species recovery strategies. However, as the standard of practices matures, tools that more efficiently facilitate its implementation are needed to both tackle projects at larger scales and consistently track outcomes across diverse settings. Therefore, a standard workflow to support and document projects from design through implementation is required.

2.0 TECHNICAL SPECIFICATIONS

The required design documentation work-flow must follow the basic design principles established by the LTPBR manual to guide users in their site assessment and then their project design. As is typical of all other restoration project tracking templates, site evaluations and on-the-ground response are necessary components. However, with process-based restoration support, it will be necessary to also capture the design rationale, expected outcomes and project management requirements as the practitioner’s engagement with a project is on-going over many years, and potentially multiple implementers and project managers. Thus, a design framework that collects information in a way it can be easily shared and communicated is lacking. While there are many successful examples of people implementing their own workflows to follow the LTPBR standards of practice, having a full project life-cycle design and documentation framework will facilitate practitioners’ flexibly and enable the community to consistently follow the LTPBR practice as initially envisioned, but most importantly, as needed for accountability and public trust in the restoration methodology.

All phases of the pre- and post-assessment, as well as the design documentation will be specified in a manner that is consistent with the business logic of Riverscapes projects. The business logic and data-dictionary based approach will support future build-out and make all current output compliant with standard Riverscape Health assessments as riverscapes-compliant projects that can be shared in the Riverscapes Warehouse (http://data.riverscapes.xyz) and ultimately be visualized with a community standard symbology.

1. Design Protocol – Workflow for reach to watershed-scale LTPBR design covering the following elements

a. Riverscapes context setting

i. Spatially nested catchment to reach typing

ii. Flow and sediment potential

b. Current / historical assessment

i. Flow

ii. Vegetation

iii. Floodplain surfaces

c. Restoration potential assessment

i. Flow and riparian zone of influence identification

ii. Geomorphic control point identification

iii. Infrastructure and land-use conflict identification

d. Complex design

i. Structure type, location identification

ii. Structured intended function identification

iii. Structure to complex specific performance indicators

e. Evaluation design

i. Evaluation template

1. Spatial-temporal revisit design

2. Evaluation information template

ii. Structure to complex to watershed summary template

2. Data dictionary

a. Design vocabulary

b. Implementation vocabulary

c. Assessment vocabulary

d. Inter-dependence and relationship diagraming

3. Work-flow dependencies

a. Identify information sources and potential alternatives

i. Topography

ii. Flow

iii. Vegetation

b. Logic framework for information table relationships

4. Forms

a. Watershed assessment information template

b. Reach-scale complex design information template

c. Reach-scale implementation design information template

d. Reach-scale post-construction assessment information template

5. Prototype examples

a. Annotated worked example of watershed assessment

b. Annotated worked example of reach-scale complex design

c. Annotated worked example of implementation design

d. Annotated worked example of post-construction assessment design Build-out to an electronic information management platform is not in this scope of work; however, all design and documentation considerations must be driven by the potential to utilize these specifications and the information resulting from their prototyping as a platform architecture design and a suite of use-cases.

3.0 DELIVERABLES & SCHEDULE

Deliverable The deliverable for this work order is a design, implementation and evaluation template for the full life-cycle of LTPBR projects. The tool will facilitate the assessment of riverscape health at different snapshots in time to support the LTPBR planning and design process, as well as facilitate the consistent, repeatable design of structures, complexes and zones of influence. The tool will also provide the framework for post-project evaluation and assessment to facilitate communication of project outcomes relative to initial expectations.

Schedule Preliminary products are to be reviewed by vendor and TOC on a regular (at least once per month) basis. Invoicing for progress is allowed if on-going progress meetings confirm work done to date. The final product is due within one year from the date of the award.

4.0 PERIOD OF PERFORMANCE

The period of performance for this contract is one year from the date of award.

5.0 PLACE OF PERFORMANCE

The contractor is responsible for performing in core business hours Monday through Friday except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. Work will normally be performed at the contractor’s place of business, or usual work locations. Remote work is authorized and will be monitored through regular (weekly) communication with NWFSC TOC.

6.0 SECURITY

· Personnel performing work must wear visible identification at all times when physically within Government facilities or on Government premises.

· Personnel performing work will not work on-site.

· Personnel performing work will not require access to NOAA facilities.

· Personnel performing work will not require a PIV or CAC.

· Personnel performing work will not require a NOAA email address.

· Personnel performing work will not require use of DOC owned IT Equipment (Laptop, Desktop Computer).

· Personnel performing work will not require Non-Government IT equipment to interconnect to a DOC network.

· Personnel performing work will not require access to non-public DOC/NOAA data.

7.0 DATA PRIVACY

Should work on this agreement require that personnel have access to Privacy information, personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations.

Data created, obtained and collected during the performance of this agreement is the property of NMFS. Data may not be released by any party without written consent from the NMFS POC. Data must be protected from unauthorized disclosure. Personnel must comply with all Federal, DOC, NOAA, and NMFS policies relating to IT and data security.

8.0 NON-PERSONAL SERVICE

Personnel performing services under this order will be controlled, directed and supervised at all times by management personnel of the contractor. Personnel will perform independent of and without the supervision of any Government official. Actions of contractor employees may not be interpreted or implemented in any manner that results in any employee creating or modifying Federal policy, obligating the appropriated funds of the U.S. Government, overseeing the work of Federal employees, providing direct personal services to any Federal employee or otherwise violating the prohibitions set forth in Parts 7.5 and 37.1 of the Federal Acquisition Regulations. The NMFS will perform the inspection and acceptance of the completed work.