NOIS2 Sample RFTP.pdf

NOIS2‐XXX‐RFTP (based on RFTP Template V.1.34) Page 1

NASA Open Innovation Services 2 (NOIS2)

Sample Request for Task Plan (RFTP)

RFTP Number: NOIS2‐XXX‐RFTP‐00A Date: XX‐XX‐202X

Project Name: Plausible, Demonstrable Methods Sought for Eliminating Harmful Emissions from the Aircraft

Transportation Sector

Project Owner Organization/Office:

Proposal Due Date: Proposals are due on X/XX/XXXX at 5:00 PM Central time

Notice of Intent: Award of the final task order will be made based on the availability of funding.

Proposals in response to this solicitation will be valid for 120 Days unless otherwise proposed.

Points of Contact:

hq‐coeci‐nois@mail.nasa.gov

, Contracting Officer (CO)

, Contract Specialist (CS)

, Contracting Officer’s Representative (COR)

, Contracting Officer’s Representative (COR)

NOIS2‐XXX‐RFTP (based on RFTP Template V.1.34) Page 2

Proposal Submittals: Proposal forms shall be submitted electronically via the following link.

<link>

RFTP Questions: All questions regarding this solicitation shall be submitted through the RFTP

Question Submission Form <link>, no later than X/XX/XXXX at 12:00 PM Central time. All final questions and answers will be shared with all of the NASA Open Innovation Services 2 (NOIS2) contractors on the NOIS2 Contractor Resources Site at <link>.

Pricing Information:

For proposal planning and pricing purposes, contractors should assume a not‐to‐exceed amount of $XX,XXX for this work (including prize purse).

Task Order Award Type:

This Task Order is a Small Business Set‐Aside, meaning it is reserved for exclusive competitive participation by small businesses, 8(a) participants, HUBZone small business concerns, service‐ disabled veteran‐owned small business concerns, economically disadvantaged women‐owned small business (EDWOSB) concerns, and women‐owned small business (WOSB) concerns.

Proposals will only be accepted from contractors that identify as small based on the criteria for

NAICS code 541990 All Other Professional, Scientific and Technical Services ‐ $16.5M in average annual receipts. The Government will utilize the information available in the applicable repository to verify the contractor’s small business status.

Project Authority: Procurement

● The purpose of this project is to acquire a solution for the direct benefit/use of the

United States Government

● Vendor pays prize purse (include prize purse in proposed price)

● International Participation allowed

Prescribed project methodology:

● Any method

NOIS2‐XXX‐RFTP (based on RFTP Template V.1.34) Page 3

Statement of Work

1.0 Overview

1.1. Project Synopsis

NASA is looking for fresh new ideas, especially those not previously explored, for making aviation as benign to the environment as it can be. The focus is on the elimination of harmful emissions, or the direct, in‐flight elimination of the harm caused by emissions, from narrow and wide‐body aircraft which typically travel for more than 2 hours.

1.2. Background of the Problem

Currently, almost all airplanes use gas turbines to provide the power to generate sufficient thrust and lift for flight. Jet A is the most common fuel burned after mixing with compressed air in a combustor. The byproducts of that combustion are expanded through a turbine to generate torque to turn propulsive fans. These byproducts contain carbon dioxide, nitrous oxides, nVPM

(soot), water, and other molecules. Carbon Dioxide stays in the air for decades and is known to cause global warming. Water in the form of contrails cause aircraft induced cloudiness which can trap heat may also cause global warming despite the time scale for persistence being much smaller in minutes to hours. Soot facilitates the creation of contrails as nucleation sites for ice formation in the right conditions. Nitrous oxides can also have a negative climate effect.

The number of global air transportation vehicles is expected to grow 2.9% each year for the next

10 years. More aircraft means more emissions and, as other sectors of transportation decarbonize, the percent contribution to universal global CO2 emissions by aviation will increase dramatically. Aviation is the hardest transportation sector to decarbonize, but there are some ideas for how to do it. The United States has set a climate goal to achieve net‐zero carbon emissions in the U.S. aviation sector by 2050. There is a plan in place for achieving that goal. See:

https://www.faa.gov/sites/faa.gov/files/2021‐11/Aviation_Climate_Action_Plan.pdf

The primary method to do so is through use of Sustainable Aviation Fuel which will eventually be produced using mostly green energy sources such as wind, solar, and nuclear. This is a huge challenge which is not without issues.

NASA University Innovation is looking for fresh new ideas on how to eliminate negative effects of air travel on the planet’s environment with new technologies to mitigate or eliminate the harm associated with aircraft emissions.

Below is a list of some of potential areas that could help aviation achieve net zero by 2050 plus those that could push beyond that towards a true zero emission future by a later date. Your idea might include one or more of these (but is certainly not limited to them):

1. New, or non‐carbon‐based fuels, produced in a green manner which are burned in a

NOIS2‐XXX‐RFTP (based on RFTP Template V.1.34) Page 4 combustor or utilized by a fuel cell on the vehicle, without producing CO2 as a byproduct.

2. Use of alternative energy sources for providing controllable thrust.

3. Carbon Dioxide captured from the atmosphere and used to create fuel which is then used to produce alternative noncarbon‐based green aviation fuels.

4. Modifications of, or additives to, turbine engine air intake, compressor flow, combustion, or turbine flow.

5. Filtering or changing the turbine outlet exhaust to mitigate CO2 and other harmful emissions.

6. 5‐10x more power dense fuel cells.

7. Game‐changing battery chemistries or super‐capacitors.

8. Highly Efficient closed hybrid cycle power systems.

9. Hybrid Electric Propulsion.

10. Re‐mapping of the hub‐and‐spoke system to reduce the overall number of flights while still meeting passenger demand.

11. Development of new vehicle designs that are significantly more aerodynamically efficient.

Example: Transonic Truss Braced Wing (TTBW) concept.

1.3. Project Description

The purpose of this solicitation is to look beyond the use of Sustainable Aviation Fuels to offset emissions produced during all modes of aircraft operation. Direct methods of eliminating harmful emission chemicals are desired. Although global warming by way of atmospheric CO2 is the primary driver for change, other emissions are also problematic. Ideas should address these as well. Emissions such as water, NOx, and nVPM (soot), are of concern. The NASA University

Innovation (UI) Project (https://uli.arc.nasa.gov/) has funded ideas from US universities but now is looking for fresh new ideas from a wider community. UI is preferably looking for ideas that have not been previously explored for making aviation as benign to the environment as it can be.

Concepts should be plausible and demonstrable. They should also at some point in the future, be sustainable for the entire global aviation sector.

For this initial activity, NASA is seeking white papers describing ideas that can reduce harmful aviation emissions. White papers must include a plausible description of how they could be demonstrated.

Note: The NASA UI Program has plans for a follow‐on development effort where all solvers (US and non‐US) partner with a US based academic institution to demonstrate the feasibility of their solution. Solvers must identify any limitations that would preclude partnering with a US academic institution to further advance their ideas to reduce emissions. Solver proposals will be evaluated based upon the adherence to the request, the idea’s innovativeness, and the plausibility/credibility of their demonstration plans. Any future follow‐on effort is subject to funding availability.

2.0 Task Order Requirements

2.1. Project and Participant Specific Requirements

NOIS2‐XXX‐RFTP (based on RFTP Template V.1.34) Page 5

2.1.1. The Contractor shall deliver a solution(s) that consist of 7‐to‐10‐page white papers that describes:

2.1.1.1. A plausible technical method for significantly reducing or eliminating harmful emissions from flights of 2 or more hours.

2.1.1.2. Quantified estimates of the benefits that can be achieved

2.1.1.3. A credible plan for demonstrating that the proposed emissions reduction method is viable (For future funding, demonstration plans must involve US academic institution for collaboration)

2.1.1.4. Include references where appropriate

2.2. Project Execution Requirements

Specific to this task order, per section 3.5 of the NOIS2 Statement of Work

(SOW), the Contractor shall:

2.2.1. Coordinate with the Government to refine project goals and requirements and translate the specific problem and/or need into a project plan to deliver the end product or service using one or more of the methodologies listed in Section 3.2 of the NOIS2 SOW. This may include problem analysis and decomposition, problem/challenge statement development, evaluation criteria, etc.

2.2.2. Provide access to a community and an established process for facilitating matching that community to successfully meet the requirements specified in the individual Request for Task Plan.

2.2.3. Provide access to the tools required to fully support the management and conduct of the project effort for the defined community.

2.2.4. Coordinate project execution with all project stakeholders.

2.2.5. Comply with the specific Intellectual Property (IP) rights/licensing for any delivered product/solutions identified in the task order to enable the Government to fully utilize the deliverable for its intended purpose.

2.2.6. Execute the task order

2.2.7. Provide and support recommended solutions for hosting any necessary data, algorithms, or computer infrastructure.

2.2.8. Conduct media coordination and outreach to advertise task order defined projects and build participation and engagement.

2.2.8.1. Provide marketing and outreach that promotes the participation of underserved and/or minority communities and educational institutions.

2.2.8.2. Comply with Government specified timelines for the review of media products (typically at least 10 business days).

2.2.9. Execute/Coordinate a defined process for solution/product submission, evaluation, and selection based on task order requirements. This process will be supported by Government participation and feedback as needed.

NOIS2‐XXX‐RFTP (based on RFTP Template V.1.34) Page 6

2.2.10. Provide an appropriate and complete compensation/award system for community members including the vendor‐specific process and documentation required where the award results in the transfer or management of Intellectual Property (IP) rights, details of licensing agreements, and any additional documentation for the delivered end product or service.

2.2.11. Execute a defined process to ensure any community/crowd participants receiving compensation under a given task order are eligible to receive payment under the laws of the United States.

2.2.12. Resolve any questions, issues, and disputes with community/crowd members during or following a project.

2.2.13. Deliver end products resulting from the task order execution to the Government.

2.2.14. Support the installation and/or integration of products/solutions. For digital products, this includes delivery to an online data repository accessible by the Government.

2.2.15. Provide training for any Contractor‐specific platform(s) or process(es).

2.2.16. The Contractor shall screen solution submissions against evaluation criteria and coordinate the evaluation process.

2.2.17. Intellectual Property: The contractor shall provide the Government with an irrevocable, royalty‐free, non‐exclusive, worldwide license to use for all deliverables outlined in this Task Order. The contractor shall provide the delivered solutions to the government under unlimited rights as specified in clause FAR 52.227‐14 Rights in Data‐‐General (May 2014) and as modified by

NFS 1852.227‐14, Rights in Data‐‐General (April 2015). Unlimited rights means the rights for the Government to use, disclose, reproduce, prepare derivative works, distribute copies to the public, and perform publicly and display publicly on the web or elsewhere, in any manner and for any purpose, and to have or permit others to do so. It is the responsibility of each contractor to ensure that all solutions are delivered as such, and ensure that if partnering or subcontracting, that the subcontractor(s) agree to such terms. It is also the responsibility of the contractor to ensure the participation agreement provides the aforementioned terms and the contractor notify the Contracting Officer if the company’s standard participation agreement does not outline such terms.

3.0 Schedule Constraints and Period of Performance

3.1. Project Schedule

The Contractor should complete the requirements in this Task Order and make all solutions available no later than X/XX/XXXX

3.2. Period of Performance

NOIS2‐XXX‐RFTP (based on RFTP Template V.1.34) Page 7

All milestones contained in the Task Order must be completed by X/XX/XXXX.

4.0 Reporting and Data Requirements

4.1. Task Order Specific NOIS2 SOW Reporting and Data Requirements

As required by Section 3.6 of the NOIS2 SOW, the Contractor shall provide status reporting for every executed task order project. Typical task order reporting includes specified metrics, program reviews, periodic status reports, and a project close‐out report.

4.2. Project Reporting Process

Following the Project Kick‐off meeting, the designated contractor Point of

Contact (POC) will receive an email with a link to a web form containing the Pre‐

Project Launch Reporting fields. In the case of a challenge, the POC shall complete and submit this form no later than two days before the project launch

(go‐live). When the project concludes, the designated POC will receive a second email with a link to a web form containing the project close‐out reporting fields.

In the case of a challenge, the Contractor POC shall complete and submit this form no later than two weeks following the announcement of the challenge winner(s).

4.3. Project Data

The Contractor shall provide the following data for this project:

4.3.1. A brief overview of the project (350 words or less) for promotional purposes

4.3.2. Total Project Budget (including prize purse if applicable)

4.3.3. Challenge Related Data (if applicable)

4.3.3.1. Challenge website link

4.3.3.1.1. If there are multiple challenge URLs, provide one link that will point to all competitions in the campaign (one link per

RFTP). This will allow challenge.gov to point to one URL for the project's duration. This should be provided before launching the first challenge. The contractor‐provided site’s content can be updated as subsequent challenges within the campaign are launched.

4.3.3.2. Challenge Start Date

4.3.3.3. Challenge Close Date

4.3.3.4. Challenge Award Amount (Monetary, if multiple, total prize pool)

4.3.3.5. Challenge Winner Announcement Date (if multiple, just final)

NOIS2‐XXX‐RFTP (based on RFTP Template V.1.34) Page 8

4.3.3.6. Description of Challenge Marketing Approach

4.3.3.7. Hi‐resolution challenge image (1045x320 minimum)

4.3.3.8. Contestant demographic info (location, age, employment, sex, etc.) (as available)

4.3.3.9. Challenge Metrics

4.3.3.9.1. Number of Active Challenge Participants

4.3.3.9.2. Number of Registered Participants

4.3.3.9.3. Number of Unique Solvers

4.3.3.9.4. Number of Challenge Submissions

4.3.3.9.5. Number of Countries with Solvers/Submitters

4.3.3.10. Algorithm Challenge Data

4.3.3.10.1. Algorithm contest scoring data

4.3.3.10.2. Algorithm verification data

4.3.3.11. Challenge.gov Posting: The Contractor shall draft the required posting for Challenge.gov to include:

4.3.3.11.1. The subject of the challenge

4.3.3.11.2. Participation eligibility rules

4.3.3.11.3. Participant registration process

4.3.3.11.4. Prize amounts

4.3.3.11.5. The basis on which a winner will be selected

4.3.4. Statistics on the efficacy of marketing approaches (analytics on project page origination, navigation, etc.); retweets; events; other engagements

(as available, if applicable)

4.3.5. Links, files, and other Project‐related assets, including publications, analysis, press releases, multimedia, and other marketing materials (as available, if applicable)

4.3.6. Description of the Evaluation Criteria and the Judging Process

4.3.7. Description of Product/Results/Research Advancement

4.3.8. Lessons Learned

4.3.9. Software Related Data

4.3.9.1. User/Admin/Installation manuals/documentation

4.3.9.2. Test documentation

4.3.10. Total contractor‐government meeting hours

4.3.11. The project close‐out report shall be presented to the stakeholders at a close‐out meeting to review results, solicit feedback on the effectiveness of project processes and results, and discuss lessons learned. Contractor attendance in person is not required.

NOIS2‐XXX‐RFTP (based on RFTP Template V.1.34) Page 9

4.3.12. Complete Form JSC‐1679‐EZ Form, Disclosure of Invention and New

Technology (Including Software), for each solution being transferred to the Government. Refer to JSC Form 1679‐EZ Blank Form and Sample

Form with Instructions on the NOIS2 Contractor Resources website NOIS2

Files area.

4.3.13. In the case that winning solution(s) are based on NASA technology or software, [the Contractor shall] verify that the winner(s) have successfully completed the licensing process for relevant NASA technologies and/or provide a copy of the Software Usage Agreement for software downloads.

5.0 Task Plan Proposal Preparation Requirements

The Contractor shall use the online NOIS2 RFTP Proposal Submission Form at <link> to submit all proposal information. This form captures the information required for the proposal submission as described below (Associated form field names and form sections are noted in bold):

5.1. Identifying Information

5.1.1. Submitting Contractor’s Email address

5.1.2. RFTP ‐ Select the RFTP to which this proposal is a response (selected from the list on the form).

5.1.3. Contractor’s Name ‐ Name of NOIS2 Contractor Submitting Plan.

(selected from the list on the form)

5.1.4. Submitter’s Name ‐ This should be an authorized representative for the contractor.

5.1.5. Submitter’s Phone Number

5.2. Contractor’s Proposal for Task Order Execution ‐ Any NOIS2 vendor selected to perform this Task Order shall meet all the requirements listed in the RFTP. This section is intended to capture the specific approach planned for executing this

Task Order.

5.2.1. Project Start Date ‐ Assumed project schedule start date to show the proposed project timeline. Task Order start date is as of CO signature on the Task Order, unless otherwise proposed.

5.2.2. Project End Date ‐ Proposed project completion date (based on the assumed project start date above) to show the proposed project timeline.

NOIS2‐XXX‐RFTP (based on RFTP Template V.1.34) Page 10

5.2.3. Total Price (USD) ‐ Total price in US Dollars to execute the proposed Task

Order (including any prize awards if applicable). Provide in the price proposal a full life cycle firm fixed price to conduct the project.

5.2.4. Proposal Narrative (Uploaded PDF Attachment) ‐ Provide a PDF document no longer than 5 pages including the following narrative information. Hyperlinks may only be provided for past projects as allowed by Section 5.2.4.2. Do not use hyperlinks anywhere else in your proposal. Additional hyperlinks included anywhere else in the proposal will not be evaluated. If alternate approaches are proposed, the contractor may utilize two additional pages, for a total of 7 pages. The alternate approach(es) must be clearly identified, and begin on a separate page to allow for clear traceability of page count. The two additional pages may only contain content dedicated to the alternate approach(es).

5.2.4.1. Description of Technical Approach/Plan: Describe the proposed technical approach for meeting the requirements. If optional phases are proposed, include a description here. This should include a price basis of estimate that describes the “elements” included to execute the proposed plan to meet the effort described in this RFTP. This shall include but not be limited to the following:

5.2.4.1.1. Individual and total award amounts (inclusive of direct community member payments if applicable).

5.2.4.1.2. Management and Execution Fees with a rationale based on the specific elements of project execution that meet the Contractor’s business model.

5.2.4.1.3. If optional phases are proposed, specify associated fees and award amounts as well as the total price with and without the optional phase(s).

5.2.4.1.4. External entity expenses (i.e., data hosting or

computational services, etc.)

5.2.4.2. Rationale for Selection: Describe why you or your community is best suited to provide the products/services outlined in the RFTP.

You may include brief descriptions and/or web links to past projects that support this description.

5.2.4.3. Additional Information: Provide any additional information that you feel is needed by the Government to assess your proposal. If

NOIS2‐XXX‐RFTP (based on RFTP Template V.1.34) Page 11 optional phases are proposed, specify associated fees and award amounts as well as the total price with and without the optional phase(s). You may also use this section to discuss any alternative approaches or recommendations to enhance project execution

(including schedule and price associated with an alternative approach). If the Contractor believes the estimated task order

NTE value is insufficient to achieve a successful result or can improve the overall value to the Government, the Contractor may submit rationale and justification for the need to exceed the estimated task order value and the associated price as described earlier in this section.

5.2.5. Challenge Proposal Data (if applicable) ‐ This section captures the proposal details associated with a challenge or series of challenges if the

Contractor indicated “Yes” in the “Proposing a challenge?” prompt.

5.2.5.1. Prize Pool Amount (USD) ‐ Proposed prize pool amount in US

Dollars if applicable

5.2.5.2. Prize Structure and/or Phasing ‐ Describe the recommended prize structure (along with any contest phasing as needed) for the proposed challenge(s) if applicable (see form for character limit).

5.2.5.3. Challenge Launch Date ‐ Proposed challenge launch date (if applicable) based on the assumed project start date above to show the proposed project timeline.

5.2.5.4. Challenge Submission Deadline ‐ Proposed challenge submission deadline date (if applicable) based on the assumed project start date above to show the proposed project timeline.

5.3. Proposed Teaming Arrangements

Offerors that choose to propose a Task Order teaming arrangement with another NOIS2 contractor or outside vendor must propose an arrangement utilizing a prime and subcontractor relationship.

5.3.1. The prime contractor will assume all legal responsibility under the Task

Order.

5.3.2. The Task Order will be awarded to the prime contractor, and invoices will only be paid to the prime contractor.

5.3.3. When proposing a teaming arrangement, the prime contractor submitting the proposal will be requested to provide teaming arrangement documentation during the Milestone negotiation phase.

The teaming arrangement documentation must disclose the identity of

NOIS2‐XXX‐RFTP (based on RFTP Template V.1.34) Page 12 the subcontractor and the details of the teaming arrangement and fully disclose the company relationships.

5.4. Number of Allowable Proposal Submissions

Each NOIS2 Contractor may submit up to one proposal as the prime contractor, in response to this RFTP. If multiple proposal submissions are submitted by one contractor, the Government will evaluate only the latest submitted proposal and will discard any previous versions or submissions. However, there are no limitations to the number of times a contractor may be listed as a subcontractor in other companies' proposals.

6.0 Evaluation Criteria

6.1. Evaluation

The Evaluation Panel will consider the factors below and will rate each proposal on a scale from 1‐10 based on how well the proposed plan provides the

Government with the greatest value and highest probability of success in meeting the TO requirements.

6.1.1. Factor 1: Technical Approach

The Government will evaluate each proposal to determine if the offeror’s proposed technical approach meets the TO requirements. The

Government will evaluate the overall technical merit of the proposal.

6.1.2. Factor 2: Schedule, Management, and Communications

The Government will evaluate the proposed approach toward managing, communicating, and reporting required to meet the TO objectives.

6.1.3. Factor 3: Price

The Government will evaluate the proposed price in comparison with the scope of work contained in the proposal.

6.2. Selection and Award

This RFTP is conducted under the fair opportunity guidelines of FAR 16.505.

Vendors are hereby instructed that, regardless of any language that may be used in this solicitation, the Government is not conducting this procurement under

FAR Part 15. The TO award will be made based on a determination of the best value to the Government based on the factors outlined in this RFTP. The

Government will perform a comparative analysis to select the contractor that is best suited to fulfill the requirements. The Government may interact with any contractor(s) during the proposal evaluation period, enter into one‐on‐one meetings, ask questions, or receive additional information to better understand the proposal(s). The Government may request an updated proposal(s) as a result

NOIS2‐XXX‐RFTP (based on RFTP Template V.1.34) Page 13 of the interactions the Government has with the contractor(s). The proposal alterations may apply to price, schedule, technical requirements, or any other area of the proposal. Once the Government selects the best‐suited contractor(s)

(the apparent successful offeror(s)), the Government reserves the right to communicate with only that contractor(s) to address Milestone Payment details and finalize the TO with that contractor(s). If the parties cannot successfully resolve any remaining issues, the Government reserves the right to communicate with the next best‐suited contractor(s). TO performance shall begin when the written direction is provided via email from the CO. The RFTP does not commit the Government to award a Task Order nor does it obligate the

Government for costs incurred in the preparation and submission of proposals in anticipation of a Task Order.

6.3. Personnel Notice

NASA may use contractor support personnel to provide technical, business, and investment expertise when evaluating proposals. Any support contractor involved in the evaluation process will be bound by appropriate nondisclosure agreements to protect proprietary and project‐sensitive information and must have accepted limitations on future contracting.