SVTT Development Plan for Open Flight Demo NRA (06172026).pdf

NATIONAL AERONAUTICS AND SPACE

ADMINISTRATION (NASA)

NASA Subsonic Vehicle Technologies and Tools (SVTT) Project

NASA Glenn Research Center (GRC) NASA Research Announcement (NRA) for

Development Plan for Open Fan Flight Demonstration

ANNOUNCEMENT NUMBER:

80GRC026R0002

NRA ISSUED: June 17, 2026

KEY DATES

Questions Due: June 27, 2026, 5:00 PM EDT

Proposals Due: August 3, 2026, 5:00PM EDT

Contents

OVERVIEW

1. INTRODUCTION

2. BACKGROUND

3. OPEN FAN FLIGHT DEMONSTRATION PLAN DEVELOPMENT

4. APPROACH

4.1. Project Management

4.2. Open Fan Propulsion Flight Demonstration Plan Development Approach

4.2.1. Open Fan Flight Demonstration Plan Development Tasks:

4.2.2. Open Fan Flight Demonstration Risk Mitigation Tasks (optional):

5. EXPECTED OUTCOMES AND DELIVERABLES

5.1 Technology Plan and Metrics

5.2 Documentation

6. INTELLECTUAL PROPERTY

7. REVIEWS AND DOCUMENTATION

8. ELIGIBILITY INFORMATION

8.1. Eligibility

8.2. Number of Proposals and Teaming Arrangements

8.3. Programmatic Considerations

9. PROPOSAL AND SUBMISSION INFORMATION

9.1. Electronic Submission of Proposals – Proposal Marking and Delivery Through NASA’s EFSS Box (MAY 2026)

9.1.1. Technical Content 13

10. PROPOSAL REVIEW INFORMATION

10.1. Evaluation Criteria

10.1.1 Technical Evaluation

10.1.2. Overall Evaluation for Award

10.2. Partial Awards and Participation with Others

11. PROVISIONS

12. Representations and Certifications

13. SUMMARY OF KEY INFORMATION

14. LIST OF ATTACHMENTS

OVERVIEW

This Glenn Research Center (GRC) Center-Level NASA Research Announcement (NRA) is issued in accordance with the NASA Federal Acquisition Regulation (FAR) Supplement (NFS).

This Subsonic Vehicle Technologies and Tools (SVTT) Project solicitation seeks an open fan flight demonstration plan with optional accompanying risk reduction activities. Whereas a traditional RFP provides the Government’s defined Statement of Work (SOW), this NRA relies on Offerors to submit a Work Plan in the form of a SOW as part of their proposal that, if selected, is intended to become the SOW included in Section C on any awarded contract(s). In addition, this NRA includes a Model Contract (see Attachment A) with all potential clauses that will be included in the final contract(s) to inform Offerors of NASA’s expectations to expedite contract award at the conclusion of this NRA.

Upon completion of the NRA proposal evaluations, NASA intends to award hybrid contract(s) (CLIN 01- Firm Fixed Price (FFP) and CLIN 02 – Cost Plus Fixed Fee (CPFF)) to Offerors who best meet the goals set forth in this NRA. A competitive range will not be established, and final proposal revisions shall not be requested/accepted. If an Offeror’s proposal is selected at the conclusion of the Final NRA evaluation period, NASA will advise the Offeror that the Government intends on entering into negotiations and will follow up with a contract that includes (if necessary), modifications contemplated in the Offeror's SOW, and request agreement or identification of any exceptions. Any necessary negotiations will be conducted in accordance with FAR Subparts 15.3 and 15.4.

Issuing Office: NASA Glenn Research Center

Office of Procurement, MS 60-1 21000 Brookpark Road Cleveland, OH 44135-3127

Agency Contact(s):

Hunter C. Butkovic, Contract Specialist, Phone: (216) 433-3110, Email: hunter.c.butkovic@nasa.gov

Brianna Lindsey, Contracting Officer, Phone: (216) 433-5675, Email: brianna.lindsey@nasa.gov

1. INTRODUCTION

As part of the NASA Advanced Air Vehicles Program (AAVP), the SVTT Project endeavors to advance knowledge, technologies, and concepts that enable accelerated introduction of radical aircraft and engine technologies across a range of vehicle classes. The SVTT portfolio consists of technology maturation activities applicable to a broad range of vehicles, including commercial subsonic aircraft of various classes and vertical lift vehicles as an emerging transportation mode.

The portfolio also covers technology target entry-into-service (EIS) opportunities for the 2030s as well as those in the 2040s. SVTT seeks to increase the Technology Readiness Level (TRL) of technologies to accelerate the rate of implementation by U.S. industry. This is achieved through partnerships with industry to ensure that these technologies are applicable to planned products to increase the chances of inclusion in future aircraft systems.

This NRA solicits proposals for providing an open fan flight demonstration plan with optional accompanying risk reduction activities. The flight demonstration plan will inform SVTT of the scope of a possible future flight demonstration and provide insight into the roadmap, risk reduction areas, and areas of potential investment.

[End of Section]

2. BACKGROUND

The Research and Technology Mission Directorate (RTMD) (formerly, the Aeronautics Research Mission Directorate (ARMD)) has reorganized with new projects to align with revised priorities for future aircraft technology. A new SVTT Project has been established within NASA’s AAVP. The SVTT Project consolidates select elements of three previous NASA Projects: Revolutionary Vertical Lift Technology (RVLT), Advanced Air Transport Technology (AATT), and the Hybrid Thermally Efficient Core (HyTEC). SVTT intends to advance knowledge, technologies, and concepts that enable accelerated introduction of radical aircraft and engine technologies across a range of vehicle classes. Research activities are applicable to a broad range of vehicles, including commercial subsonic aircraft of various classes and vertical lift vehicles and will cover a wide range of TRL and EIS vehicle opportunities. The diverse portfolio is envisioned to include conceptual development of future vehicles, disruptive emerging technology, as well as technology development activities for nearer-term vehicles. The higher TRL areas will likely focus primarily on vehicles intended for EIS in the 2030s, and the lower TRL, paradigm shifting technology, will be focused for 2040s EIS and beyond. Conceptual vehicle studies will be performed in parallel that incorporate advanced technologies to inform future aircraft configurations. This solicitation is targeting higher TRL and the 2030s timeframe and is specific to the flight demonstration and integration of an open fan propulsor.

3. OPEN FAN FLIGHT DEMONSTRATION PLAN DEVELOPMENT

Open fan propulsors promise substantial fuel-burn reduction and increased efficiency for single-aisle aircraft. Accurately predicting integrated/installed benefits is a significant barrier because open fans strongly couple aerodynamics, acoustics, structures, and aircraft configuration and current ground and wind tunnel tests cannot fully capture all installation and operational effects.

As a result, well instrumented flight testing is essential to validate models, derisk certification, and quantify real world performance and noise. The objective is to develop a comprehensive plan that defines the requirements, scope, and feasibility of an open fan flight demonstration. The deliverables will address technical, operational, and certification considerations, including aerodynamic integration, structural impacts, noise and emissions performance, and propulsion system reliability.

The scope is limited to single-aisle class aircraft with the following attributes:

• 150–180 passengers

• 3,500 nm design range; 900 nm economical range

• Cruise Mach 0.78–0.82

• Span at gate fits within 118 ft width constraint

4. APPROACH

The goal of this solicitation is to obtain an open fan flight demonstration plan that will inform future NASA activities. The period of performance is six (6) months for the Open Fan Flight Demonstration Plan Development and up to twelve (12) months for risk mitigation task to run in parallel. This section contains key tasks to be carried out.

4.1. Project Management

Conduct the project management activities needed to supervise, direct, and manage the development of the flight demonstration plan. Project management and planning tools shall be used to ensure the accomplishment of each work element in a timely manner and within budget constraints. This task includes planning, monitoring, analysis and presentation of Offeror cost, schedule, and technical performance.

4.2. Open Fan Propulsion Flight Demonstration Plan Development Approach

The Open Fan Propulsion Flight Demonstration Plan will inform subsequent phases of technology development and demonstration planning, ensuring alignment with industry needs and regulatory standards. The flight demonstration plan development will include a summary of the findings and an analysis of market offerings. The summary and flight demonstration is focused specifically on the open fan element of the propulsion system and its efficient integration with the aircraft. The following summarizes the key items to address in this solicitation:

• Address technical, operational, and certification considerations, including aerodynamic integration, structural impacts, noise and emissions, and propulsion system reliability.

• Provide an analysis of market offerings and investment strategies for narrowbody advanced propulsion technologies.

• Provide a summary of findings and recommendations for subsequent technology development and demonstration planning.

• Provide final plan which details findings, investment strategies, and market analysis.

4.2.1. Open Fan Flight Demonstration Plan Development Tasks:

1. Assuming an introduction into the fleet in the 2035 to 2040 timeframe, develop and provide an analysis of the Offeror’s next generation single-aisle transport vision system that uses open fan propulsors. This may include vision system configuration and architectures other than traditional tube and wing transports.

Provide a detailed description of the preferred vision system and vision system architecture (including 3 view and entry into service date).

2. Develop and provide comprehensive Technology/Configuration/Architecture Development Plans, including use of required ground and flight demonstrations.

Ground demonstrations may be needed to advance technology/architecture/configuration readiness and/or may be needed to effectively and safely develop a flight demonstrator. Include starting, intermediate, and finishing TRL levels aligned with ground and flight demonstrations.

3. Develop & provide key performance parameters, technical performance parameters, technical performance indicators associated with Offeror preferred ground and flight demonstrations. Associate and link key performance parameters with the Vision System and associate the Technical Performance parameters with the desired ground and flight demonstrations.

4. Develop and provide system and subsystem requirements for key enabling ground and flight demonstrations.

5. Develop and provide technical, and risk-infused cost and schedule plans for Offeror preferred ground and flight demonstrations. Show costs and schedule tasks for design, fabrication, procurement, assembly, and integration/checkout of each major aircraft and advanced technology subsystem for both ground and flight demonstrations.

6. Describe & provide required partnerships and interfaces for Offeror preferred ground and flight demonstrations. Describe in detail potential cost share or risk strategies and percentages with the U.S. Government.

7. Develop & deliver a System Integration approach for enabling ground and flight

8. Develop & provide a Human System Integration approach for Offeror preferred ground and flight demonstrations.

9. Develop & provide Offeror’s concept of operations of the preferred ground and flight demonstrations. Assuming jointly conducted flight test operations with NASA, identify by scenario, team makeup and roles, as well as any needed government furnished hardware or facilities. Identify the major heritage hardware and software assumptions and associated risks with preferred ground and flight

10. Develop & provide detailed risk assessments (technical, cost and schedule) with associated risk mitigation plans for Offeror preferred ground and flight demonstrations. Include a list of the top 10 risks using a 5x5 Likelihood / Consequence scoring method and link the risk mitigation plans and steps to the proposed cost/schedule plans.

4.2.2. Open Fan Flight Demonstration Risk Mitigation Tasks (optional):

Develop and deliver separate technical approaches and cost proposals for up to three risk mitigation task plans to effectively accelerate proposed flight demonstration.

• Risk Mitigation Task 1 (optional)

• Risk Mitigation Task 2 (optional)

• Risk Mitigation Task 3 (optional)

5. EXPECTED OUTCOMES AND DELIVERABLES

5.1 Technology Plan and Metrics

Offeror shall submit a roadmap to show how the open fan propulsion concept will evolve over time and the path to a potential future vision product. Offeror shall indicate the key technology maturation activities and gaps. The proposal shall define what activities will occur during the contract and what gaps are expected to remain that would need to be addressed in the future.

5.2 Documentation

The Offeror shall use the United States Customary Units (USCU) – length (ft), force (lbf), temperature (deg F), mass (slug), and time (s) as the primary set of units in conjunction with equivalent SI units shown in parentheses.

The Offeror shall use the NASA BOX system for deliverables and exchange of technical material.

The required deliverables of a successfully awarded contract are outlined in Section 7.

All deliverables shall be delivered in the expected period of performance of the contract.

6. INTELLECTUAL PROPERTY

Data Rights. Normally, the Government has unlimited rights in technical data created under a NASA agreement. Knowledge gained about key parameters related to proposed technology, resulting from the analysis of the test data by NASA researchers, shall become the property of NASA, as long as it does not disclose company proprietary geometry or specific performance parameters. The knowledge gained by NASA shall be publishable and unlimited immediately after the testing and analysis is complete. Delivery or third-party licensing of proprietary software or data developed solely at private expense will not normally be required except as specifically negotiated in a particular agreement to satisfy NASA's own needs or to ensure the commercialization of technology developed under a NASA agreement.

A clear statement is required of what intellectual property is expected to be available to the Government, U.S. Aeronautics Community, and Public at the conclusion of the work. It is NASA’s preference that all deliverables under the contract be provided to NASA with unrestricted/unlimited rights; thus, any restrictions must demonstrate a significant net benefit to the Government.

A Model Contract is provided as Attachment A, with a sample Pre-Award Data Rights Assertion Table (DRAT) provided as Attachment 1 to the Model Contract.

Patent Rights. The Government will have certain statutory rights in an invention that is conceived or first actually reduced to practice under a NASA award. 51 U.S.C. 20135 provides that title to such inventions vests in the United States, except where 35 U.S.C. 202 provides otherwise for nonprofit organizations or small business firms. However, NASA may waive all or any part of the rights of the United States subject to certain conditions.

7. REVIEWS AND DOCUMENTATION

The desired reviews and documentation of a successfully awarded contract include:

Project Coordination

• Technical and schedule progress monthly meeting (or as agreed upon and held remotely) to assess progress

• Mid-point Contract Review

• Final Contract review

Reviews

• Kick-off review

• Mid-point review

• Final Review

Documentation

• Monthly: status of the technical, financial, and schedule progress (Microsoft PowerPoint, limited version only)

• Monthly and Quarterly 533 financial status

• Mid-point contract review presentation (Microsoft PowerPoint, limited version only)

• Final flight demonstration plan (Microsoft Word format, limited and unlimited versions) o The plan shall be inclusive of the results of the entire contract, recommendations, and conclusions o The plan shall be prepared in accordance with NASA FAR Supplement (NFS)

1852.235-73 (DEVIATION AUG 2025)

• Final Oral Presentation and document (Microsoft PowerPoint, limited and unlimited versions) o The final contract review shall consist of a public and Government-only review o NASA requires two versions of the presentation, one with non-proprietary content suitable for presenting in a public forum and one for NASA Government review only

Data Rights Identification

Any technical data or computer software developed, delivered, or used under this contract (including reviews and documentation) for which the Offeror anticipates that the Government will receive less than Unlimited Rights must be identified on the Data Rights Assertion Table (See Model Contract Section H for instruction) and appropriately marked at the lowest segregable level. Limited Rights technical data must be identified and marked at the lowest segregable level pertaining to an item, component, or process and Restricted Computer Software data must be identified and marked at the lowest segregable level pertaining to computer software.

8. ELIGIBILITY INFORMATION

8.1. Eligibility

Participation in this program is open to all categories of U.S. organizations, including educational institutions, industry, and not-for-profit institutions. Historically black colleges and universities, other minority universities, small disadvantaged businesses, veteran-owned small businesses, service-disabled veteran-owned small businesses, historically under-utilized business zone small businesses, and women-owned small businesses are encouraged to apply.

Participation by non-U.S. organizations is not permitted.

The contract type is Hybrid. CLIN 01 will be FFP and CLIN 02 will be CPFF (see Section 9 regarding eligibility).

8.2. Number of Proposals and Teaming Arrangements

NASA recognizes and supports the benefits of having diverse and inclusive scientific, engineering, and technology communities and fully expects that such values will be reflected in the composition of all panels and teams, including peer review panels (science, engineering, and technology), proposal teams, science definition teams, and mission and instrument teams.

There is no restriction on the number of proposals that an organization may submit to this solicitation or on the teaming arrangements for any one proposal. However, each must have a separate SOW, schedule, and cost document for evaluation purposes.

NASA reserves the right to select only part of a proposed activity, often at a level of support reduced from that requested in the original proposal, and/or may select a combination of proposals that best meets the objectives of this NRA. NASA also reserves the right to select only those portions of any proposal that align with these objectives. Offerors should specify if a proposal is offered as a nonseparable package of work. Additionally, NASA may decide to award an effort for less than the full period of performance. In these cases, the Offeror will be given the opportunity to accept or decline such selection. If the Offeror accepts such an offer, a revised budget and SOW may be required before funding action on the proposal can be initiated. If the Offeror declines the offer of a partial selection, or participation in a joint investigation, the offer of selection may be withdrawn in its entirety by NASA.

To assist determining prices/costs for a partial award, the Price/Cost Proposal shall be split into separate CLINs and SLINs. See Section 9 for more details.

Teaming Arrangements with non-U.S. organizations is not permitted. NASA funding through this NRA may not be used to support research and development efforts by non-U.S.

organizations at any level.

8.3. Programmatic Considerations

Currently, the total Government estimate for the NRA is anticipated to be $5.0M, dependent upon NASA funding profiles. The actual number and value of the awards will depend on the quality and cost of the proposals received and the availability of Government funds.

9. PROPOSAL AND SUBMISSION INFORMATION

9.1. Electronic Submission of Proposals – Proposal Marking and Delivery Through NASA’s

EFSS Box (MAY 2026)

Proposals shall be submitted and received by August 3, 2026, by 5:00 p.m. EDT

(a) The offeror must submit its proposal via NASA’s Enterprise File Sharing and Sync Box (EFSS Box), a FedRAMP Moderate certified platform. Electronic submissions must not contain hidden formulas, tables, be locked, be password protected, or contain links to data not included in the electronic copy. All electronic submissions should be searchable and should not contain scanned documents, except those documents that must be provided in their native format (e.g., signature pages, prior award fee letters for past performance, DCAA/DCMA approval letters, as applicable). The offeror must ensure documents are free from viruses and malware, as documents determined by NASA to contain a virus or malware will not be opened or evaluated.

Subcontractors may submit their required proposal information separately using the instructions in this provision. The offeror must ensure subcontractor submissions are made no later than the date and time specified for proposal submission and comply with all solicitation instructions.

(b) Prior to the submission of proposal files, offerors interested in submitting a proposal in response to this solicitation should notify both Contract Specialist, Hunter Butkovic, and Contracting Officer, Brianna Lindsey of their intent to submit a proposal at least 48 hours prior to the intended submission date, at the following email address(es): hunter.c.butkovic@nasa.gov and brianna.lindsey@nasa.gov.

Offerors, especially those that have not previously submitted a proposal utilizing NASA’s EFSS Box, should coordinate the submission of a test file with both hunter.c.butkovic@nasa.gov and brianna.lindsey@nasa.gov no less than five (5) days in advance of the proposal due date specified in the solicitation to allow time to work through any submission issues.

(c) The offeror must submit all proposal files to:

https://nasagov.app.box.com/f/7c27eb3190154e6d8959528542087dc1. The offeror must follow instructions regarding proposal submission found at https://www.hq.nasa.gov/office/procurement/other/EFSS-Box-Offeror-Proposal-Submission- Instructions.pdf.

(d) Offerors should electronically submit their proposals not later than 5:00 p.m. EDT one working day prior to the date specified for receipt of proposals, if offerors seek to coordinate with the contracting specialist/officer regarding the proposal’s receipt. NASA is not required to verify proposal receipt prior to the submission deadline.

(e) Offerors are encouraged to include all individual proposal files within a single .zip file.

Electronic file names must be limited to letters, numbers, dashes, and single spaces, except for the period that is required before the file extension (e.g., .zip, .pdf), in order to successfully upload and download files from the EFSS Box system. The offeror must not use special characters “/” or “\” in file names. The offeror must sequentially number each file and clearly label the contents of the file and include the name of the offeror and subcontractor name (if applicable) in the individual file name. Examples of acceptable individual file names are as follows (not specific to this solicitation):

For Proposal File Submissions:

1. Offeror name 80GRC026R0002 Technical Topic - Past Experience.pdf

2. Offeror name 80GRC026R0002 Technical Topic - Technical Approach and

Capabilities.pdf

3. Offeror name 80GRC026R0002 Technical Topic - Proposed Statement of Work

4. Offeror name 80GRC026R0002 Technical Topic - Price/Cost Volume

5. Offeror name 80GRC026R0002 Technical Topic - Business Volume.pdf

6. Offeror name 80GRC026R0002 Technical Topic - Signed Model Contracts and

Provisions

7. Offeror name 80GRC026R0002 Technical Topic - Eligibility Certification and

Supplemental Information Form

Note: Regarding Price/Cost Volume: Financial data and other numerical figures may also be provided in Excel format and labeled clearly.

Individual files cannot exceed 150GB per file. Submitted files must not include password protection. Unless specifically authorized by the solicitation instructions, alternate proposal submissions must not be submitted.

(f) Immediately after all files have been uploaded and the proposal has been submitted in its entirety, the offeror is requested to notify both Contract Specialist, Hunter Butkovic, and Contracting Officer, Brianna Lindsey at the following email address(es) hunter.c.butkovic@nasa.gov and brianna.lindsey@nasa.gov with a listing of all documents by filename that were submitted via EFSS Box. If any problems are experienced with the EFSS Box system (e.g., login, file transfer), please contact Contract Specialist, Hunter Butkovic, and Contracting Officer, Brianna Lindsey via e-mail as soon as possible.

(g) The offeror is responsible for ensuring its proposal reaches the Government office designated in the solicitation by the date and time specified in the solicitation. The Government

The Offeror shall describe experience providing goods and services performed in the past three

(3) years that are of a similar size, scope, and complexity to the proposed work. Include any work related to the proposed technology area such as current and pending support.

Section III – Technical Approach and Capabilities

a. Overall Approach:

The Offeror shall describe the technical approach. The description shall include the anticipated key technical challenges and risks and an assessment of the approach and credibility of the flight demonstration plan.

b. Technology Roadmap The Offeror shall provide a summary of relevant current capabilities and how they fit into the roadmap for the proposed flight demonstration plan, including technology development steps and any supporting risk reduction activities.

c. Key Personnel:

The Offeror shall describe the qualifications of the principal investigator and key team members.

The description shall include the experience and breadth of the team, experience related to the technical topic, experience in advanced technology development for aviation, experience advanced composite materials or propulsion airframe integration development, and the ability to offer innovative approaches. The Offeror shall discuss how those qualifications will enable the team to successfully perform the proposed work.

d. Risk Reduction Activities (Optional) The Offeror shall describe any risk reduction activities proposed that support the associated flight demonstration plan and the value that they add.

Section IV - Proposed Statement(s) of Work

a. Overall SOW:

The Offeror shall provide the Work Plan(s) written as a SOW to perform the proposed contribution or development. The Work Plan(s) shall include the proposed schedule for meeting the objectives, management approach, and the use of the Offeror’s resources.

Although not required it is advised the Offeror follows the format in the provided SOW Template (Attachment D).

b. Intellectual Property:

Identify intellectual property that will be limited and publicly available at the conclusion of the work. Data Rights Assertions shall be captured and included as an attachment to the Offeror’s submitted model contract. An example of the format for the Data Rights Assertions Table can be found as Attachment 1 of the Model contract.

c. Deliverables:

Within the requested Work Plan, written as a SOW, the Offeror shall describe the topic-oriented outcomes and data and/or information which will be produced and incorporated into the appropriate deliverable.

Section V – Price/Cost

The proposal shall provide a budget justification for each CLIN/SLIN/year and be supported by appropriate details by cost category. Attachment B of this Announcement shall be used for the price/cost proposal submittal and contains required price/cost proposal. Offerors may add or remove CLINs/SLINs to Attachment B, based upon proposed CLIN structure. Attachment B, Price/Cost Proposal shall identify the Offeror’s price/estimated costs.

It is anticipated that adequate price competition may be obtained under this solicitation.

Therefore, the submission of certified cost or pricing data is not required pursuant to FAR 15.403-1(b)(1).

This price/cost section shall encompass all costs associated with the requirements of the proposed contract and comply with applicable NFS regulations. As applicable, include separate estimates for salaries and wages; fringe benefits; equipment; materials and supplies; services;

travel; subcontract; other miscellaneous identifiable direct costs; and indirect costs.

To facilitate partial awards, the following CLIN structure is requested. Offerors shall clearly document all proposed activities in Section B of the Model Contract. Each proposal shall be separated into two CLINs, one for the flight demonstration plan portion of the proposal and one for any optional risk reduction activities. Furthermore, activities shall be proposed and priced separately as a subcontract line item (SLIN) as shown below:

Example CLIN/SLIN Structure:

CLIN 01: Open Fan Flight Demonstration Plan Development SLIN 001: Task 1 SLIN 002: Task 2 SLIN 003: Task 3 SLIN 004: Task 4 SLIN 005: Task 5 SLIN 006: Task 6 SLIN 007: Task 7 SLIN 008: Task 8 SLIN 009: Task 9 SLIN 010: Task 10

CLIN 02: Open Fan Flight Demonstration Risk Mitigation Tasks

SLIN 001: Risk Reduction Activity 1

SLIN 002: Risk Reduction Activity 2 SLIN 003: Risk Reduction Activity 3

Section VI – Business Volume

Offeror shall provide the below information:

1. Business Systems

State whether all business systems, including but not limited to accounting, property control, purchasing, estimating, and employee compensation, which require Government acceptance or approval (as applicable) are currently accepted/approved without condition.

Provide the date of acceptance/approval for each system and the cognizant contract administration office. Explain any existing conditional acceptances/approvals and the compliance status of any system(s) for which acceptance or approval is currently withheld.

To receive a cost-reimbursement contract (CLIN 02), FAR 16.204-3 requires that a contractor's accounting system be adequate for determining costs applicable to the contract prior to the award of a cost-reimbursement contract. Accordingly, the contractor MUST provide evidence of an adequate accounting system as determined by the cognizant administrative office for accumulating and reporting incurred costs. If relying on the accounting system adequacy of a Joint Venture team member, sister company, or any other affiliated company’s accounting system, demonstrate a convincing basis for using that system as a basis for determining adequacy. A cost-type contract can only be awarded to an offeror that has been determined to have an adequate accounting system.

If proposing to CLIN 02 and do not have an approved accounting system pursuant to FAR 16.301-3(a)(2), the Offeror shall submit a completed Standard Form (SF) 1408 or a completed DCAA Pre-Award Accounting System Survey Checklist along with the Offeror’s accounting system policies and procedures as part of their proposal.

Offerors may employ, based on their sole discretion, and at no cost to the Government a Certified Public Accountant (CPA) who is in good standing, who should prepare and execute an audit program designed for the evaluation of the Offeror’s accounting system pursuant to Generally Accepted Accounting Principles (GAAP) and the requirements identified on SF 1408 ‘PreAward Survey of Prospective Contractor Accounting System.’ A properly executed SF 1408 signed in block 3 by the auditor should be included in the Offeror’s proposal.

In lieu of submitting SF 1408 as outlined above, the Offeror may submit a completed DCAA Pre-Award Accounting System Survey Checklist. If submitting the Checklist, the Offeror shall also provide their accounting system policies and procedures as part of their proposal.

For Offerors who do not have an approved accounting system and opt to submit the DCAA Pre- Award Accounting System Survey Checklist in lieu of the SF 1408, completed by a CPA firm, the determination of eligibility to receive a cost type contract will be made be by the NASA Cognizant Federal Agency (CFA) office only for apparent successful Offeror(s).

The Offeror shall also provide an explanation of all changes to its accounting system since the last audit/review or approval by the cognizant Government Audit Agency (GAA) or Administrative Contracting Officer (ACO). If the most recent GAA or ACO audit or review expressed an inadequate determination of the accounting system, the Offeror shall provide a detailed explanation of the status of the corrective action plan and any corrective actions that have been taken to date.

2. Summary of Exceptions Include a statement of acceptance or list all specific exceptions to any terms and conditions included in the model contract and all contract attachments.

Include the reason for any exception, new terms, conditions, and/or clauses, including any proposed benefit to the Government. This list must include all exception(s), deviation(s) and/or conditional assumptions taken and be supported by sufficient justification to permit evaluation.

3. Contract Administration Furnish the information listed below:

a. Cognizant Government audit agency with mailing address, email address, telephone number, and fax number.

b. Cognizant Government inspection agency with mailing address, email address, telephone number, and fax number.

c. Cognizant Government Administrative Contracting Officer by name with mailing address, email address, telephone number, and fax number.

4. Waiver of Rights to Inventions This solicitation contains NFS clause 1852.227-70, “New Technology—Other than a Small Business Firm or Nonprofit Organization” and NFS provision 1852.227-71, “Request for Waiver to Rights to Inventions”. Any petitions for advance (prior to contract execution) waiver of rights to inventions shall be included in this volume.

5. Subcontracting Plan In accordance with FAR 52.219-9, a subcontracting plan shall be required for the apparent successful Offeror(s) with any proposal over $900,000 unless a small business is proposing as a prime contractor. If no subcontracting opportunities exist, the Offeror shall provide a detailed statement as to why no such opportunities exist. Subcontracting Plan, if required, will be requested during negotiations.

NRA Attachment A - Signed Model Contract(s)

A Model Contract is provided in Attachment A of this announcement. A Model Contract shall be provided for each proposal, signed by an official authorized to contractually bind the Offeror.

This can be done by signing the attached SF33 on the first page of the Model Contract. Please be advised that all sections designated with the text [OFI] represent “Offeror Fill-Ins”. Offerors shall fill in [OFI]’s and submit as part of the signed Model Contract with the proposal submittal.

Additionally, sections designated with the text [TBD] stand for “To Be Determined”. Offerors should not fill in the [TBD]’s. The Government will update these prior to contract award.

Offerors may take exception to, or have unique interpretations of, any Model Contract clauses.

These exceptions and/or unique interpretations shall be listed clearly in the Summary of Exceptions, noted within item No. 2 above. Note, taking exception to, or having unique interpretations of any required clauses MAY have a negative impact on potential selection. Each proposal shall provide a Data Rights Assertions Table as an attachment to the Model Contract.

NRA Attachment C - Eligibility and Compliance Certification The Eligibility and Compliance Certification Questionnaire File shall be completed by the Offeror and each of the Offeror’s partners listed in the proposal’s Teaming Approach (see Section 8 above) that will be supporting the partner’s research and technology development efforts.

Oral Presentation All Offerors who are determined to be eligible based off the administrative review and past experience will be invited to give a Technical Oral Presentation via Microsoft Teams Meeting.

The Oral Presentation is for technical proposal summarization and clarification purposes only.

No material changes to the proposal can be made during the Oral Presentation. If there is a material discrepancy between the written proposal and the Oral Presentation the written proposal shall prevail. Any material changes or supplemental information will not be considered.

Oral presentation should summarize the technical portion of the proposal and shall be no longer than 10 minutes and an additional 15 minutes will be allotted for any clarifying technical questions from NASA. However, NASA reserves the right to adjust the time allotted based on the quantity and/or quality of proposals received.

The Technical Oral Presentation will be recorded for documentation purposes.

10. PROPOSAL REVIEW INFORMATION

Each proposal will be evaluated by a NASA panel to assess the proposal’s intrinsic scientific and technical merit, its relevance to the SVTT objectives, and its cost realism and price reasonableness. These factors will also go into evaluating the proposal’s best value to the agency and SVTT Project. Each proposal will be evaluated and scored on its own merits using the criteria described below.

Potential for Success:

The Government will evaluate the proposal to determine credibility of the potential for success given the key technical challenges, risks and means to address them, and the Offeror’s capabilities, related experience, facilities, techniques, or unique combination of these which are integral factors for achieving the proposal's objectives.

Overall Approach:

The Government will evaluate the proposal to determine the credibility, feasibility, and comprehensiveness of the proposed technical approach to address the items outlined in Section 4 while providing a comprehensive understanding of current state-of-the-art capabilities and methods to overcoming identified technical challenges and risks.

Ambition and Innovation:

The Government will evaluate the proposal and assert a higher value on plans that provide more ambitious or innovative (but still credible) efforts to their technical approach. Examples of this more ambitious approach:

• Open fan flight demonstration that implements a coupled airframe propulsion installation representative of an Offeror’s vision aircraft versus using a flying test bed to simply carry an open fan propulsor.

Key Personnel:

The Government will evaluate the proposal to determine the suitability of the proposed team based on their qualifications and assess their potential for success in the proposed work.

Risk Reduction Activities (Optional) The government will evaluate Risk Reduction Activities included within the proposal to determine their credibility, effectiveness, and value in overcoming the technical challenges and risks.

Section IV – Price/Cost Although the Price/Cost Factor is not numerically scored nor receives an adjectival rating, it is important in determining that the Offeror understands the solicitation and the resources required.

The Price/Cost factor is used to determine what the Offeror’s proposal will likely cost the Government should it be selected for award.

The price/proposed cost will be assessed to determine reasonableness and cost realism, as well as form the basis for selection. The evaluation will be conducted in accordance with FAR 15.404.

A cost realism analysis will be conducted to ensure that a realistic price is determined and considered by the Government. Offerors should refer to FAR 2.101 for a definition of “cost realism” and to FAR 15.404-3(b) for a discussion of “probable cost”. As noted in FAR 15.404- 3(a), the cost realism analysis consists of “independently reviewing and evaluating specific

NASA reserves the right to select for award one, multiple, or none of the proposals received in response to this NRA.

10.2. Partial Awards and Participation with Others

NASA reserves the right to select only a portion of a proposed activity, usually at a level of support reduced from that requested in the original proposal. Offerors should specify if a proposal is offered as a non-separable package of work. Additionally, NASA may decide to award an effort for less than the full period of the proposal. In these cases, the Offeror will be given the opportunity to accept or decline such selection. If the Offeror accepts such an offer, a revised budget and SOW may be required before funding action on the proposal can be initiated.

If the Offeror declines the offer of a partial selection, or participation in a joint investigation, the offer of selection may be withdrawn in its entirety by NASA.

11. PROVISIONS

A subset of provisions within this Section are incorporated by reference, with the same force and effect as if they were given in full text. Provisions incorporated by reference which require a fill-in by the Government include the text of the affected paragraph(s) only. This does not limit the provision to the affected paragraph(s). The Offeror is responsible for understanding and complying with the entire provision. The full text of the provision is available at the addresses contained in provision 52.252-1, Solicitation Provisions Incorporated by Reference.

FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1):

52.203-11 CERTIFICATION AND DISCLOSURE REGARDING PAYMENTS TO

INFLUENCE CERTAIN FEDERAL TRANSACTIONS. (SEP 2024)

52.203-18 PROHIBITION ON CONTRACTING WITH ENTITIES THAT REQUIRE

CERTAIN INTERNAL CONFIDENTIALITY AGREEMENTS OR STATEMENTS-

REPRESENTATION. (JAN 2017)

52.204-5 WOMEN-OWNED BUSINESS (OTHER THAN SMALL BUSINESS). (OCT 2014)

52.204-7 SYSTEM FOR AWARD MANAGEMENT—REGISTRATION. (SEP 2025)

(DEVIATION)

52.209-2 PROHIBITION ON CONTRACTING WITH INVERTED DOMESTIC

CORPORATIONS-REPRESENTATION. (DEC 2025) (DEVIATION)

52.214-34 SUBMISSION OF OFFERS IN THE ENGLISH LANGUAGE. (APR 1991)

52.214-35 SUBMISSION OF OFFERS IN U.S. CURRENCY. (APR 1991)

52.215-16 FACILITIES CAPITAL COST OF MONEY. (JUN 2003)

52.215-22 LIMITATIONS ON PASS-THROUGH CHARGES—IDENTIFICATION OF

SUBCONTRACT EFFORT. (DEC 2025) (DEVIATION)

52.222-56 CERTIFICATION REGARDING TRAFFICKING IN PERSONS COMPLIANCE

PLAN. (DEC 2025) (DEVIATION)

52.225-2 BUY AMERICAN CERTIFICATE. (OCT 2022)

52.233-2 SERVICE OF PROTEST. (SEP 2025) (DEVIATION)

52.240-90 SECURITY PROHIBITIONS AND EXCLUSIONS REPRESENTATIONS AND

CERTIFICATIONS. (DEVIATION SEP 2025)

(End of FAR by reference provisions)

NASA FAR SUPPLEMENT (48 CFR CHAPTER 18) PROVISIONS:

1852.227-71 REQUESTS FOR WAIVER OF RIGHTS TO INVENTIONS. (JAN 2026)

(DEVIATION)

1852.227-84 PATENT RIGHTS CLAUSES. (APR 2015)

1852.228-80 INSURANCE-IMMUNITY FROM TORT LIABILITY. (SEP 2025)

(DEVIATION)

1852.233-70 PROTEST TO NASA. (SEP 2025) (DEVIATION)

1852.235-72 INSTRUCTIONS FOR RESPONDING TO NASA RESEARCH

ANNOUNCEMENTS. (AUG 2025) (DEVIATION)

(End of NFS by reference provisions)

52.216-1 TYPE OF CONTRACT (DEC 2025) (DEVIATION)

The Government contemplates award of Hybrid contract resulting from this solicitation.

CLIN 01 – Firm Fixed Price CLIN 02 – Cost Plus Fixed Fee

(End of provision)

52.219-1 SMALL BUSINESS PROGRAM REPRESENTATIONS. (FEB 2026) (DEVIATION)

(a) Definitions. As used in this provision-

Economically disadvantaged women-owned small business (EDWOSB) concern means a small business concern that is at least 51 percent directly and unconditionally owned by, and the management and daily business operations of which are controlled by, one or more women who are citizens of the United States and who are economically disadvantaged in accordance with 13 CFR part 127, and the concern is certified by SBA or an approved third-party certifier in accordance with 13 CFR 127.300. It automatically qualifies as a women-owned small business concern eligible under the WOSB Program.

HUBZone small business concern means a small business concern that meets the requirements described in 13 CFR 126.200, is certified by the Small Business Administration (SBA) and designated by SBA as a HUBZone small business concern in the Small Business Search (SBS) (13 CFR 126.103).

Service-disabled veteran-owned small business (SDVOSB) concern eligible under the SDVOSB Program means an SDVOSB concern that is designated in the System for Award Management (SAM) as certified by the Small Business Administration (SBA) in accordance with 13 CFR 128.300.

Small business concern—

(1) Means a concern, including its affiliates, that is independently owned and operated, not dominant in its field of operation, and qualified as a small business under the criteria in 13 CFR part 121 and the size standard in paragraph (b) of this provision.

(2) Affiliates, as used in this definition, means business concerns, one of whom directly or indirectly controls or has the power to control the others, or a third party or parties control or have the power to control the others. In determining whether affiliation exists, consideration is given to all appropriate factors including common ownership, common management, and contractual relationships. SBA determines affiliation based on the factors set forth at 13 CFR 121.103.

Small disadvantaged business concern means a small business concern that-

(1) Is at least 51 percent unconditionally and directly owned (as defined at 13 CFR 124.105) by one or more socially disadvantaged (as defined at 13 CFR 124.103) and economically disadvantaged (as defined at 13 CFR 124.104) individuals who are citizens of the United States, and

(2) The management and daily business operations of which are controlled (as defined at 13 CFR 124.106) by individuals who meet the criteria in paragraph (1) of this definition.

Women-owned small business (WOSB) concern eligible under the WOSB Program (in accordance with 13 CFR part 127) means a small business concern that is at least 51 percent directly and unconditionally owned by, and the management and daily business operations of which are controlled by, one or more women who are citizens of the United States, and the concern is certified by SBA or an approved third-party certifier in accordance with 13 CFR 127.300.

(b)

(1) The North American Industry Classification System (NAICS) code for this acquisition is 541715.

(2) The small business size standard is 1,500.

(3) The small business size standard for a concern that submits an offer, other than on a construction or service acquisition, but proposes to furnish an end item that it did not itself manufacture, process, or produce (i.e., nonmanufacturer), is 500 employees, or 150 employees for information technology value-added resellers under NAICS code 541519, if the acquisition—

(i) Is set aside for small business and has a value above the simplified acquisition threshold;

(ii) Uses the HUBZone price evaluation preference regardless of dollar value, unless the offeror waives the price evaluation preference; or

(iii) Is an 8(a), HUBZone, service-disabled veteran-owned, economically disadvantaged women-owned, or women-owned small business set-aside or sole-source award regardless of dollar value.

(c) Representations.

(1) The offeror represents as part of its offer that—

(i) it □ is, □ is not a small business concern; or

(ii) It □ is, □ is not a small business joint venture that complies with the requirements of 13 CFR 121.103(h) and 13 CFR 125.8(a) and (b). [ The offeror shall enter the name and unique entity identifier of each party to the joint venture: __.]

(2) [Complete only if the offeror represented itself as a small business concern in paragraph (c)(1) of this provision.] The offeror represents that it □ is, □ is not a women-owned small disadvantage business concern.

(3) Women-owned small business (WOSB) joint venture eligible under the WOSB Program. The offeror represents as part of its offer that it □ is, □ is not a joint venture that complies with the requirements of 13 CFR 127.506(a) through (c).

[ The offeror shall enter the name and unique entity identifier of each party to the joint venture: __.]

(4) Economically disadvantaged women-owned small business (EDWOSB) joint venture. The offeror represents as part of its offer that it □ is, □ is not a joint venture that complies with the requirements of 13 CFR 127.506(a) through (c).

[ The offeror shall enter the name and unique entity identifier of each party to the joint venture: __.]

(5) SDVOSB joint venture eligible under the SDVOSB Program. [Complete only if the offeror is certified as a SDVOSB concern]. The offeror represents as part of its offer that it □ is, □ is not a SDVOSB joint venture eligible under the SDVOSB Program that complies with the requirements of 13 CFR 128.402. [ The offeror shall enter the name and unique entity identifier of each party to the joint venture:__.]

(6) HUBZone joint venture eligible under the HUBZone Program. [Complete only if the offeror is a HUBZone small business concern.] The offeror represents, as part of its offer, that it □ is, □ is not a HUBZone joint venture that complies with the requirements of 13 CFR 126.616(a) through (c). [ The offeror shall enter the name and unique entity identifier of each party to the joint venture: __.] Each HUBZone small business concern participating in the HUBZone joint venture must be certified as a HUBZone concern.

(d) Notice. Under 15 U.S.C. 645(d), any person who misrepresents a firm’s status as a business concern that is small, HUBZone small, small disadvantaged, service-disabled veteran-owned small, economically disadvantaged women-owned small, or women-owned small eligible under the WOSB Program in order to obtain a contract to be awarded under the preference programs established pursuant to section 8, 9, 15, 31, and 36 of the Small Business Act or any other provision of Federal law that specifically references section 8(d) for a definition of program eligibility, will be—

(1) Punished by imposition of fine,…