NASA ROSES08: Applying NASA Observations, Models and IT for Air Quality Proposal

Air Quality Cluster > Applying NASA Observations, Models and IT for Air Quality Main Page > Proposal | NASA ROSES Solicitation | Context | Resources | Schedule | Forum | Participating Groups

Proposal Cover Page incl.

Proposals submitted electronically through NSPIRES will use the NSPIRES Proposal Cover Page that is available through the World Wide Web at http://nspires.nasaprs.com/. Access for application to a given NRA is provided through a menu entitled "Solicitations" then accessing the link "Open Solicitations." Once completed by the PI, the Proposal Cover Page must be accessed in the NSPIRES system and submitted electronically by the AOR.

If a hard copy submittal is also required, the submitted cover page should then be printed and signed by the AOR. As directed in the solicitation, the signed copy must be submitted with the original copy of the proposal on or before the proposal due date. In addition, reproductions of the signed Proposal Cover Page are used to preface the required printed copies of the proposal.

NSPIRES automatically assigns a unique proposal number to each proposal only after it has been successfully submitted. NASA uses this NSPIRES number throughout the proposal review and selection process to uniquely identify the proposal and its associated electronic data. If no NSPIRES number appears on the Proposal Cover Page, then it has not been properly submitted through the NSPIRES system.

Proposal Summary 300 words

Both electronic submittal systems require the PI to prepare a Proposal Summary. The Proposal Summary should provide an overview of the proposed investigation that is suitable for release through a publicly accessible archive should the proposal be selected. The proposal summary (or abstract) should be concise, should not exceed 4000 characters in length, and should not contain any special characters or formatting. Note that, while Grants.gov does not impose a limit on the length of the proposal summary, it will be truncated when the proposal is transmitted from Grants.gov to NASA. Grants.gov users must use a writeable pdf form (downloadable from grants.gov) named ProposalSummary.pdf. This form restricts the Proposal Summary document to 4000 characters or less.

In addition to the information listed in the NASA Guidebook for Proposers, this section must explicitly state which of the eight applications areas the proposal relates to (if more than 2, then only identify the top 3). For the primary application(s) related to the project,

Table of Contents

Offerors should include a one-page Table of Contents that provides a guide to the organization and contents of the proposal. This item may also incorporate customized formats of the Proposer’s own choosing, e.g., identification of the submitting organization through use of letterhead stationary, project logos, etc. The electronic system chosen may provide some assistance in preparing the Table of Contents, but Proposers are responsible for the accuracy of proposals submitted.

Technical/Science/Management Section

[Ref.: Appendix B, Parts (c)(4), (c)(5), and in-part (c)(6)] As the main body of the proposal, this section must cover the following topics in the order given, all within the specified page limit. Unless specified otherwise in the NRA, the limit is 15 pages using the default values given in Section 2.3.1:

• The objectives and expected significance of the proposed research, especially as related to the objectives given in the NRA;
• The technical approach and methodology to be employed in conducting the proposed research, including a description of any hardware proposed to be built in order to carry out the research, as well as any special facilities of the proposing organization(s) and/or capabilities of the Proposer(s) that would be used for carrying out the work. (Note: ref. also Section 2.3.10(a) concerning the description of critical existing equipment needed for carrying out the proposed research and the Instructions for the Budget Justification in Section 2.3.10 for further discussion of costing details needed for proposals involving significant hardware, software, and/or ground systems development, and, as may be allowed by an NRA, proposals for flight instruments);
• The perceived impact of the proposed work to the state of knowledge in the field and, if the proposal is offered as a direct successor to an existing NASA award, how the proposed work is expected to build on and otherwise extend previous accomplishments supported by NASA;
• The relevance of the proposed work to past, present, and/or future NASA programs and interests or to the specific objectives given in the NRA;

January 2008 2-8

• A general plan of work, including anticipated key milestones for accomplishments, the management structure for the proposal personnel, any substantial collaboration(s) and/or use of consultant(s) that is(are) proposed to complete the investigation; and a description of the expected contribution to the proposed effort by the PI and each person as identified in one of the additional categories in Section 1.4.2, regardless of whether or not they derive support from the proposed budget.
• To facilitate data sharing where appropriate, as part of their technical proposal, the Proposer shall provide a data-sharing plan and shall provide evidence (if any) of any past data-sharing practices.

The Scientific/Technical/Management Section may contain illustrations and figures that amplify and demonstrate key points of the proposal (including milestone schedules, as appropriate). However, they must be of an easily viewed size and have self-contained captions that do not contain critical information not provided elsewhere in the proposal.

Decision-making Activities Description and Baseline Performance (2page)

This section must explicitly identify and describe the decision-making activity to be enhanced (or created) in the project. The description should describe the management, business, or policy topic or issue that it serves, including any quantitative information regarding its use. This section must identify and describe the end-user organization(s) and their responsibility and/or mandate to address the topic/issue.

This section should answer the following questions: What is the end-users’ current basis for decision-making? What is the decision-making activity? Who uses it and how do they use it in their decision-making process? What analyses does (will) it support and what actions and decisions are (will be) made? What measures/metrics do (will) its users employ to determine the value or quality of their decision-making? What are the reasons and needs for improving (creating) it?

This section must quantify the pre-project, baseline performance of the decision-making activity, using the end-users’ measures, as well as other quantitative measures the team plans to employ throughout the project to track progress. Proposals seeking to create a decision-making activity must quantify the baseline performance of the end users’ decision-making process/capability without a formal decision-making activity.

Primary Decision-Support Systems

• DataFed - Husar - Exceptional Events. Fan in: 50 States -> 10 EPA Regions -> 1 Federal EPA. Each transmits different pieces of information and we need to determine those pieces.

Other Decision-Support Systems

Same infrastructure can be used for different decision-support systems

• VIEWS - Brett/Shawn - Regional Haze
• BlueSky - Sean - Smoke
• BAMS - McHenry - Air Quality Forecasting for the public
• HTAP - Keating - Hemispheric Transport Policy

Earth Science Research Results (1page)

This section must identify the array of Earth science research results (Section 1.2 of this appendix) that the proposal will utilize. Proposals must be specific. For spacecraft observations, proposals should include the spacecraft, sensor, data product, and other specific information. For proposals involving Earth science models, this section should identify the inputs to the models as well as the predictions, forecast products, or other products from the models. For proposals involving NASA Earth science research results produced with commercial remote sensing data and geospatial information, proposals must identify the commercial inputs and sources. For proposals blending commercial products with NASA products, proposals should identify all the data and products.

Transition Approach (1p)

This section should articulate the transition plan, including specific activities to enable the end-users to adopt the enhancements to the decision support activity (or new decision support activity) and sustain their use of the Earth science products within the timeframe of the project.

Performance Measures (1p)

This section must articulate the measures (both quantitative and qualitative) the team will use to determine the outcomes, results, and value of the project. The measures should establish the potential improved performance achieved through integration of the Earth science research results. The measures should include those that the decision makers employ, as well as those used to establish the baseline performance.

Anticipated Results (1p)

This section must describe the expected results from the project. This section must state the team’s hypothesis for the expected quantitative improvement(s) over the "baseline" performance. This section should estimate the expected improvement(s) in decision-making enabled from the enhanced (new) decision-making activity and the associated socioeconomic benefits from the improved decision-making. This section should be as specific and quantitative as possible. This section should identify how the expected results will contribute to the specific goals and objectives of the related application area(s).

Project Management (1p)

This section should articulate the management approach and structure; plan of work; partnership arrangements; and the expected contribution, roles, and responsibilities of the team members. Project schedule and milestones must be included. Note: Meetings (number of, frequency of, etc.) do not qualify as project management milestones.

Statements of Commitment – Co-Is (as needed)

Every Co-Investigator and Collaborator (ref. definitions in Section 1.4.2) identified as a participant on the proposal’s cover page and/or in the proposal’s Scientific/Technical/Management Section must submit a brief, signed statement of commitment that acknowledges his/her intended participation in the proposed effort. In the case of more than one Co-I or Collaborator, a single statement signed by all participants may be submitted. In any case, each statement must be addressed to the PI, may be a facsimile of an original statement or the copy of an email (the latter must have sufficient information to unambiguously identify the sender), and is required even if the Co-I or Collaborator is from the proposing organization. An example of such a statement follows:

"I (we) acknowledge that I (we) am (are) identified by name as Co-Investigator(s) [and/or Collaborator(s)] to the investigation, entitled <name of proposal>, that is submitted by <name of Principal Investigator> to the NASA Research Announcement <alpha-numeric identifier>, and that I (we) intend to carry out all responsibilities identified for me (us) in this proposal. I (we) understand that the extent and justification of my (our) participation as stated in this proposal will be considered during peer review in determining in part the merits of this proposal. I (we) have read the entire proposal, including the management plan and budget, and I (we) agree that the proposal correctly describes my (our) commitment to the proposed investigation."

Primary Decision-Support Systems

• DataFed - Husar - Exceptional Events

Other Decision-Support Systems

• VIEWS - Brett/Shawn - Regional Haze
• BlueSky - Sean - Smoke
• BAMS - McHenry - Air Quality Forecasting for the public
• HTAP - Keating - Hemispheric Transport Policy

Data Providers/Value-Adding Mediators

• GIOVANNI - Leptouch
• NAAPS - Westphal
• AQS - Mangus
• Airnow - Dye

Letters from End-User Organizations (4 1page letters)

In addition to the brief statements from Co-Is required per Section 2.3.10 of the NASA Guidebook for Proposers, this section may include up to 4, one-page letters from the end-user organizations that will benefit from the proposed project. The letters may include input from the community and beneficiaries served by the end user organizations. All statements or letters must be addressed to the PI and included in the proposal.

Current/Pending Support

Information must be provided for all ongoing and pending projects and proposals that involve the proposing PI. This information is also required for any Co-Is who are proposed to perform a significant share (>10 percent) of the proposed work.

All current project support from whatever source (e.g., Federal, State, local or foreign government agencies, public or private foundations, industrial or other commercial organizations) must be listed. This information must also be provided for all pending proposals already submitted or submitted concurrently to other possible sponsors. Do not include the current proposal on the list of pending proposals unless it has been submitted to another possible sponsor.

All projects or activities requiring a portion of the investigators’ time during the period of the proposed effort must be included, even if they receive no salary support from the project(s). The total award amount for the entire award period covered (including indirect costs) must be shown, as well as the number of person-months per year to be devoted to the project for each year, regardless of source of support.

Specifically, for the PI and any Co-Is who are proposed to perform a significant share (>10%) of the proposed work, provide the following information:

• Title of award or project title;
• Name of PI on award;
• Program name (if appropriate) and sponsoring agency or organization, including a point of contact with his/her telephone number and email address;
• Performance period;
• Total budget; and
• Commitment by PI or Co-I in terms of person-months per year for each year.

For pending research proposals involving substantially the same kind of research as that being proposed to NASA in this proposal, the proposing PI must notify the NASA Program Officer identified for the NRA immediately of any successful proposals that are awarded any time after the proposal due date and until the time that NASA’s selections are announced.

References and citations

All references and citations given in the Scientific/Technical/Management Section must be provided using easily understood, standard abbreviations for journals and complete names for books. It is highly preferred but not required that these references include the full title of the cited paper or report.