"Developing Generalizable Approach for Coupled CyanoHAB Predictive Models" | W81EWF 23 SOI 0021

Frequently Asked Questions (FAQs)

What is the main purpose of this grant opportunity?

The goal is to support one partner in converting an existing coupled watershed and hydrodynamic modeling approach for cyanobacteria harmful algal blooms (cyanoHABs), originally developed for "Lake O," into a reusable, streamlined framework that can be applied across many freshwater systems. The emphasis is on transferability and usability so water managers can forecast bloom conditions and test nutrient-loading scenarios.

What problem is the project trying to solve?

The project aims to reduce the time and specialized expertise needed to set up and run a coupled watershed-to-waterbody cyanoHAB predictive model at new sites, while maintaining scientific rigor. It does this by standardizing and packaging the workflow (code, templates, documentation, and repeatable setup steps) so it can be deployed more broadly.

What does "coupled watershed and hydrodynamic modeling" mean in this context?

It refers to a linked workflow that connects (1) watershed nutrient sources and transport on land with (2) receiving waterbody hydrodynamics and cyanoHAB growth and movement in the water. The idea is to represent both nutrient loading from the watershed and in-water processes that influence bloom development and distribution.

What is meant by "cyanoHABs"?

CyanoHABs are cyanobacteria harmful algal blooms. The opportunity focuses on modeling and forecasting cyanoHAB dynamics in freshwater systems, particularly as influenced by watershed nutrient inputs and in-waterbody conditions.

Is this opportunity focused on new research, or on implementation and usability?

The opportunity explicitly emphasizes practical transferability and usability, not research novelty. Proposals are expected to focus on building a reusable framework, clear deliverables, documentation, and testing with intended users.

How many awards are expected?

USACE expects to make one award.

What is the funding amount?

The announced award ceiling is $250,000.

What type of funding instrument will be used?

The instrument type is a cooperative agreement, which generally indicates active involvement by USACE during the project through collaboration, technical coordination, and iterative review.

Who is offering this funding opportunity?

The opportunity is offered by the Department of Defense, Department of the Army, U.S. Army Corps of Engineers (USACE).

What is the Funding Opportunity Number and CFDA?

The Funding Opportunity Number is W81EWF 23 SOI 0021. The CFDA is 12.630.

What are the posting and closing dates listed?

The original posting date is June 20, 2023, and the original closing date is August 7, 2023.

Who is eligible to apply?

Eligibility is listed as "Others," with additional eligibility details referenced in the full announcement. Applicants are expected to confirm eligibility based on the specific language in the official notice.

What is expected in a strong proposal?

Based on the opportunity description, strong proposals are likely to: (1) tightly define the scientific and management questions the model will support; (2) present a realistic plan for assembling and validating datasets using existing HAB programs and available data; (3) prioritize reproducibility and ease of deployment through templates and automation; and (4) demonstrate that non-experts can successfully apply the workflow using the tutorial and supporting files.

What kinds of questions must applicants define in their proposals?

Proposals are expected to clearly define the specific technical questions the project will answer and link those questions to the tasks, datasets, and deliverables needed to answer them.

What does the opportunity require regarding datasets?

Applicants are expected to spell out the tasks and datasets needed (including data quality objectives). USACE encourages leveraging existing federal and state harmful algal bloom monitoring programs, ongoing HAB research activities, and already-available datasets rather than building everything from scratch.

What are "data quality objectives" in this opportunity?

The opportunity calls for proposals to include data quality objectives as part of defining the datasets needed for the work. In practice, this means specifying the quality expectations and suitability of data for modeling tasks, based on what is required to answer the project’s technical questions.

How should applicants define "success" for the project?

Applicants must define what success looks like for each task using both quantitative and qualitative criteria. Examples mentioned include model performance targets, completeness of documentation, usability results from testing, and reproducibility of runs.

What are the five major objectives of the work?

The work is organized into five major objectives: (1) develop open-source code and supporting materials that generalize the Lake O coupled modeling approach, including standardized input templates and repeatable artifacts; (2) demonstrate the generalized framework on a real-world USACE-relevant site that is already the subject of a USACE-sponsored HAB research project and identify the site early in pre-proposal; (3) produce a draft case study report that also serves as a step-by-step tutorial for non-modeling specialists, including necessary files and instructions (and practical sections like lessons learned and an FAQ); (4) deliver a final case study report incorporating feedback from non-expert beta testers; and (5) complete communication and reporting deliverables including a fact sheet, quarterly progress reports, draft and final case study reports with electronic files, and a presentation at the annual In-Progress Review.

What does "open-source code and supporting materials" include?

The opportunity describes deliverables that include open-source model code plus supporting materials needed to make setup and execution repeatable at new sites. This explicitly includes standardized input file templates and other artifacts needed for repeatable configuration and runs.

What is meant by making the framework "generalized"?

Generalizing the Lake O approach means converting a site-specific coupled modeling workflow into a reusable framework that can be applied across many freshwater systems, supported by standardized templates, documentation, and repeatable setup steps.

Does the project require a demonstration at a real site?

Yes. The generalized framework must be demonstrated on a real-world USACE-relevant site that is already part of a USACE-sponsored HAB research project.

When must the demonstration field site be identified?

The chosen field site has to be identified early, in the pre-proposal stage.

Is the demonstration meant to be a quick test or a full proof of transferability?

It is meant to serve as a proof of transferability. The intent is to show the approach can be applied to a different freshwater system or water resource development project and still produce a usable coupled modeling configuration, with findings captured in a case study report.

What is the purpose of the case study report?

The case study report is intended to capture outcomes and key findings from applying the generalized framework to the chosen USACE-relevant site. It also functions as a vehicle for making the framework understandable and usable for practitioners.

What is required in the draft case study report?

The draft case study report must double as a step-by-step tutorial aimed at water managers and practitioners who are not modeling specialists. It should include the necessary files, user guides, and clear instructions to support implementation, and it is expected to include practical sections like lessons learned and an FAQ.

Why does the draft tutorial need to include lessons learned and an FAQ?

The opportunity signals that USACE wants the final product to reflect real-world hurdles (such as data gaps, calibration challenges, and workflow pitfalls) and provide practical guidance on how to address them.

What is required in the final case study report?

The final case study report must incorporate feedback from non-expert beta testers. The expectation is that documentation and workflow will be improved based on what intended end users found confusing, time-consuming, or error-prone.

Who are the expected beta testers?

The opportunity specifies non-expert beta testers, meaning intended end users who are not modeling specialists, consistent with the tutorial being targeted to managers and practitioners.

What does "user-centered" mean for this project?

In this opportunity, user-centered means the framework and documentation are tested by non-experts and then improved based on their feedback, with an emphasis on clarity, reduced friction, and practical usability.

What routine reporting and communication deliverables are required?

The opportunity includes a fact sheet, quarterly progress reports, draft and final case study reports with associated electronic files, and a presentation at the annual In-Progress Review.

What is the "annual In-Progress Review" requirement?

The project must include a presentation at the annual In-Progress Review as part of the communication and reporting expectations.

What is the overall expected end product?

The intended end product is a portable, open, and manager-friendly coupled modeling package for forecasting and scenario testing of cyanoHAB dynamics driven by watershed nutrient loads and in-waterbody processes, supported by templates, documentation, and repeatable workflows.

How does this opportunity describe reproducibility expectations?

Reproducibility is highlighted as a success criterion, including reproducibility of runs. The framework is also expected to include standardized templates and artifacts that make setup and execution repeatable at new sites.

Does USACE prefer building new datasets or reusing existing monitoring and research programs?

USACE explicitly encourages teams to leverage existing federal and state HAB monitoring programs, ongoing HAB research activities, and already-available datasets, rather than building everything from scratch.

How should deliverables be structured across tasks?

Proposals are expected to lay out concrete deliverables for each task, aligned to the technical questions being answered, and include definitions of success using quantitative and qualitative criteria.