AAR_Technical_RFI.pdf
PDF 162 KB Posted
- Attached to
- Next Generation Air-refueling System (NGAS) Request for Information (RFI) Federal contract opportunity
- Solicitation number
- FA8684-NGAS
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| QA R1.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Next Generation Air-refueling System (NGAS) Request for Information (RFI)
1. Introduction
1.1. The Department of the Air Force (DAF) is pursuing continued development of the next generation of tanker concepts that address the changing strategic environment. The DAF has established the Next Generation Air-refueling System (NGAS) project to advance those efforts. The project team is conducting preliminary analysis and concept development to meet the entrance criteria for an Analysis of Alternatives (AoA) which is currently projected to begin in October 2023. The team is seeking information on innovative industry solutions that might fulfill the most stressing and complex air refueling mission requirements of the future fight.
1.2. The scope of this solution set includes the following:
1.2.1. Anticipated initial operational capability for NGAS is 2040.
1.2.2. NGAS will be the third of three increments to the Air Force tanker recapitalization plan, following increment 1 (represented by the KC-46 program) and increment 2 (known as KC-Y or “bridge tanker”).
1.2.3. NGAS shall be required to address employment in contested scenarios
1.2.4. The DAF is interested in innovative solutions in all size and performance classes that might address the stressing mission requirements; airspeeds should be compatible with modern receivers.
1.3. THIS IS A REQUEST FOR INFORMATION ONLY to understand innovative industry solutions to accomplish the NGAS mission. This RFI is issued solely for information and planning purposes. It does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This RFI does not commit the U.S. Government to contract for any supply or service. Responders are advised the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI. All costs associated with responding to this RFI will be solely at the respondent party’s expense. Not responding to this RFI does not preclude participation in any future RFP, if issued. The U.S. Government has made no final solicitation decision regarding eventual procurement or by what means such a solicitation, if any, would be handled. The information provided in this RFI is subject to change and is not binding upon the U.S.
Government. The U.S. Government has not made a commitment to procure any of the items discussed, and release of this RFI should not be construed as such a commitment or as authorization to incur costs for which reimbursement would be required or sought. All submissions become U.S. Government property and will not be returned.
2. Requested Information
2.1. Respondents should describe recommended solutions to provide the capabilities described in paragraphs 1.1 and 1.2 of this RFI. Respondents are encouraged to leverage
Next Generation Air-refueling System (NGAS) – REQUEST FOR INFORMATION experience from prior contracted efforts and/or Independent Research and Development (IR&D) activities.
2.1.1. Include, at a minimum, an architecture framework, a description of the systems and subsystems involved, and/or an evaluation of the feasibility of recommended modifications to existing systems or commercial aircraft. Provide system performance metrics including, but not limited to
2.1.1.1. Size and weight statements
2.1.1.2. Takeoff and landing, climb, cruise, and representative mission performance
2.1.1.3. Fuel offload and range
2.1.1.4. Considerations for access to regional or improvised airfields or other non-traditional basing
2.1.2. Include assessments of the maturity of potential NGAS systems and operating concepts. Address estimated timelines to field recommended solutions as well as steps required to mature proposed designs. Describe technology risks that the government should be investing in to reduce or mitigate technology maturation risks.
2.2. Your responses should further address the questions posed below along with any additional pertinent information deemed appropriate to fully characterize proposed solutions:
2.2.1. How does your solution change the way aerial refueling operations would be executed? What operational or support changes do you believe are critical to increase aerial refueling capabilities in a future fight?
2.2.1.1. How would your proposed solution increase, improve, or expand the current and planned capabilities of the tanker fleet (including KC-135, KC- 46, and Bridge Tanker)?
2.2.1.2. What considerations or restrictions does your approach require for aerodynamic compatibility with potential receivers or other tanker aircraft?
2.2.1.3. What capabilities do you propose to enable refueling of unmanned aerial systems?
2.2.1.4. How might your concept operate as an air-to-air fuel receiver?
Comment on associated potential weight and performance tradeoffs.
2.2.2. How does your system address anticipated threats to air-to-air refueling in contested operating environments in the 2040 timeframe? How might your system reduce risks for both refueler and receiver in combat scenarios? Descriptions of threat avoidance features and strategies should be general in nature such that written responses are classified at no greater than collateral secret level. Requests for submission of information at higher classifications deemed critical to the response will be addressed on a case-by-case basis.
2.2.2.1. How do you perceive the cyber threat, and what solutions do you envision that might address it?
2.2.3. What are the critical technologies that you see as essential for a viable NGAS concept? What do you assess as the greatest technical development risks?
What are the high-level cost implications for these technologies?
2.2.3.1. Concepts of varying capability and risk level (low, medium, and high) may be submitted as long as they will meet a technology availability date (TAD) of no later than 2032 (defined as all technologies achieving a technology readiness level (TRL) of 6 or higher).
2.2.4. What have you considered regarding engines and/or powerplants for your proposed solution? How would your designs address DoD strategic concerns for fuel and energy efficiency?
2.2.5. How might your system integrate within a joint air battle management network? What considerations would your system incorporate for information sharing, networking, shared situational awareness, position, navigation, and timing (PNT), and autonomy?
2.2.6. What approaches to sustainability and supportability would your solution require? What current sustainment infrastructure might be leveraged, and what new sustainment or product support requirements will be needed to ensure supportability is designed-in during early development planning?
2.2.6.1. How will your solution’s design and its sustainability approach affect its flexibility with respect to forward basing and agile combat employment?
2.2.7. How flexible is your proposed solution to future modification and adaptation in response to changing requirements? How might it incorporate current Modular Open System Architecture (MOSA) best practices?
2.2.8. How would development of your proposed solution incorporate modern Digital Engineering (DE) and/or Model-Based Systems Engineering (MBSE) best practices?
2.2.9. What ideas might you propose for innovative teaming arrangements of traditional military prime contractors with non-military contractors to achieve a mix of experience in advanced aero-configuration design, lean programs, and rapid airframe development and manufacturing?
2.2.10. What quantitative basis do you propose to assess your solution’s Reliability and Maintainability (R&M) performance attributes?
3. Responses
3.1. Interested parties are requested to respond to this RFI with a white paper not to exceed 50 pages using 12-point Times New Roman font. Any supporting technical data and digital artifacts (to include model-based designs) provided will not count against this page limit.
White papers are due no later than 2 March 2023, 1700 Eastern Time. Unclassified responses shall be submitted via secure e-mail or secure website only to the contracting officer, Mr. Christian Ryan (christian.ryan@us.af.mil), the contract specialist Ms. Megan Porter (megan.porter.5@us.af.mil), and the technical coordinator, Maj Andrew Cottle (andrew.cottle.1@us.af.mil). Classified responses up to Secret shall be coordinated with Maj Andrew Cottle (andrew.e.cottle.mil@mail.smil.mil); responses up to Top Secret, Sensitive Compartmented Information, and/or Special Access Required shall be coordinated with Mr. Michael Novy (michael.c.novy.civ@mail.smil.mil, michael.novy@af.ic.gov).
3.2. Interested parties shall follow the instructions below regarding how to deliver the white paper response package content. RFI responses shall be organized into two separate sections.
3.2.1. Section 1 of the white paper response shall provide administrative information to include the following as a minimum:
3.2.1.1. Company name, mailing address, overnight delivery address (if different from mailing address), CAGE code, phone number, fax number, and both unclassified and SIPRNet e-mail of designated point of contact.
Respondents are further requested to indicate their Foreign Ownership, Control or Influence (FOCI) status, if applicable.
3.2.2. Section 2 of the white paper response shall address the recommended approaches to address the problem identified in paragraph 1 of this RFI and provide data as requested in paragraph 2.
3.2.3. Responses should be marked, if applicable, with the appropriate controlled unclassified information (CUI) caveats, to include any ITAR restrictions.
3.2.4. Responses should NOT include marketing information, commercial documentation, or product literature.
3.3. Proprietary information, if any, MUST BE CLEARLY MARKED on the outside container and on the materials inside. The Government shall not be liable for or suffer any consequential damages for any proprietary information not properly identified. Please be advised that all submissions become Government property and will not be returned. All information received in response to this RFI that is properly marked as “proprietary” will be handled accordingly.
mailto:christian.ryan@us.af.mil mailto:megan.porter.5@us.af.mil mailto:andrew.cottle.1@us.af.mil mailto:andrew.e.cottle.mil@mail.smil.mil mailto:michael.c.novy.civ@mail.smil.mil mailto:michael.novy@af.ic.gov
3.4. Respondents are advised that employees under contract with the Government may be used to administratively process submissions and provide technical support to the Government's Analysis of Alternatives requiring access to the contractor's proprietary information. All members of the team will be reminded of their obligation to protect such information to the maximum extent permitted or required by the Economic Espionage Act, 18 U.S.C. 1831 et seq., and other applicable statutes or regulations. In addition, Government members will be reminded of their obligations to afford protection under the Trade Secrets Act, 18 U.S.C. 1905. All contractor members are required to protect the information by the terms of their contracts. These administrative support contracts include non-disclosure agreements (NDA) prohibiting contractor employees from disclosing any information submitted by other contractors or using such information for any purpose other than that for which it was furnished.
4. Questions and Industry Discussion
4.1. Questions regarding this announcement shall be submitted in writing via e-mail to the contracting officer, Mr. Christian Ryan (christian.ryan@us.af.mil), contract specialist Ms.
Megan Porter (megan.porter.5@us.af.mil), and the technical coordinator, Maj Andrew Cottle (andrew.cottle.1@us.af.mil). Verbal questions will NOT be accepted. Accordingly, questions shall NOT contain proprietary or classified information. The Government does not guarantee questions received 23 February 2023, 1700 Eastern Time, will be answered in time for the 2 March 2023 white paper submittals.
4.2. If warranted, government representatives may consolidate and disseminate general feedback to all respondents after white papers are submitted. Follow-on discussions with individual interested parties may be coordinated. The intent of any such discussions would only be to obtain additional clarification of potential capabilities to meet Government requirements and further expose risks (especially development risks).
5. Future Work
5.1. The government is evaluating an indefinite delivery, indefinite quantity (IDIQ) contract vehicle for potential future efforts (modeling, simulation, and analysis) associated with responses to this RFI (solicitation number FA8684-22-R-2006). Interested parties should contact Mr. Christian Ryan (christian.ryan@us.af.mil) and Ms. Megan Porter (megan.porter.5@us.af.mil) for further information.
mailto:christian.ryan@us.af.mil mailto:megan.porter.5@us.af.mil mailto:andrew.cottle.1@us.af.mil mailto:christian.ryan@us.af.mil mailto:megan.porter.5@us.af.mil
| 1. Introduction |
| 1.1. The Department of the Air Force (DAF) is pursuing continued development of the next generation of tanker concepts that address the changing strategic environment. The DAF has established the Next Generation Air-refueling System (NGAS) project to ... |
| 1.2. The scope of this solution set includes the following: |
| 1.2.1. Anticipated initial operational capability for NGAS is 2040. |
| 1.2.2. NGAS will be the third of three increments to the Air Force tanker recapitalization plan, following increment 1 (represented by the KC-46 program) and increment 2 (known as KC-Y or “bridge tanker”). |
| 1.2.3. NGAS shall be required to address employment in contested scenarios |
| 1.2.4. The DAF is interested in innovative solutions in all size and performance classes that might address the stressing mission requirements; airspeeds should be compatible with modern receivers. |
1.3. THIS IS A REQUEST FOR INFORMATION ONLY to understand innovative industry solutions to accomplish the NGAS mission. This RFI is issued solely for information and planning purposes. It does not constitute a Request for Proposal (RFP) or a promise t...
| 2. Requested Information |
| 2.1. Respondents should describe recommended solutions to provide the capabilities described in paragraphs 1.1 and 1.2 of this RFI. Respondents are encouraged to leverage experience from prior contracted efforts and/or Independent Research and Develop... |
| 2.1.1. Include, at a minimum, an architecture framework, a description of the systems and subsystems involved, and/or an evaluation of the feasibility of recommended modifications to existing systems or commercial aircraft. Provide system performance ... |
| 2.1.1.1. Size and weight statements |
| 2.1.1.2. Takeoff and landing, climb, cruise, and representative mission performance |
| 2.1.1.3. Fuel offload and range |
| 2.1.1.4. Considerations for access to regional or improvised airfields or other non-traditional basing |
2.1.2. Include assessments of the maturity of potential NGAS systems and operating concepts. Address estimated timelines to field recommended solutions as well as steps required to mature proposed designs. Describe technology risks that the government...
| 2.2. Your responses should further address the questions posed below along with any additional pertinent information deemed appropriate to fully characterize proposed solutions: |
| 2.2.1. How does your solution change the way aerial refueling operations would be executed? What operational or support changes do you believe are critical to increase aerial refueling capabilities in a future fight? |
| 2.2.1.1. How would your proposed solution increase, improve, or expand the current and planned capabilities of the tanker fleet (including KC-135, KC-46, and Bridge Tanker)? |
| 2.2.1.2. What considerations or restrictions does your approach require for aerodynamic compatibility with potential receivers or other tanker aircraft? |
| 2.2.1.3. What capabilities do you propose to enable refueling of unmanned aerial systems? |
| 2.2.1.4. How might your concept operate as an air-to-air fuel receiver? Comment on associated potential weight and performance tradeoffs. |
| 2.2.2. How does your system address anticipated threats to air-to-air refueling in contested operating environments in the 2040 timeframe? How might your system reduce risks for both refueler and receiver in combat scenarios? Descriptions of threat av... |
| 2.2.2.1. How do you perceive the cyber threat, and what solutions do you envision that might address it? |
| 2.2.3. What are the critical technologies that you see as essential for a viable NGAS concept? What do you assess as the greatest technical development risks? What are the high-level cost implications for these technologies? |
| 2.2.3.1. Concepts of varying capability and risk level (low, medium, and high) may be submitted as long as they will meet a technology availability date (TAD) of no later than 2032 (defined as all technologies achieving a technology readiness level (T... |
| 2.2.4. What have you considered regarding engines and/or powerplants for your proposed solution? How would your designs address DoD strategic concerns for fuel and energy efficiency? |
| 2.2.5. How might your system integrate within a joint air battle management network? What considerations would your system incorporate for information sharing, networking, shared situational awareness, position, navigation, and timing (PNT), and auton... |
| 2.2.6. What approaches to sustainability and supportability would your solution require? What current sustainment infrastructure might be leveraged, and what new sustainment or product support requirements will be needed to ensure supportability is de... |
| 2.2.6.1. How will your solution’s design and its sustainability approach affect its flexibility with respect to forward basing and agile combat employment? |
| 2.2.7. How flexible is your proposed solution to future modification and adaptation in response to changing requirements? How might it incorporate current Modular Open System Architecture (MOSA) best practices? |
| 2.2.8. How would development of your proposed solution incorporate modern Digital Engineering (DE) and/or Model-Based Systems Engineering (MBSE) best practices? |
| 2.2.9. What ideas might you propose for innovative teaming arrangements of traditional military prime contractors with non-military contractors to achieve a mix of experience in advanced aero-configuration design, lean programs, and rapid airframe dev... |
| 2.2.10. What quantitative basis do you propose to assess your solution’s Reliability and Maintainability (R&M) performance attributes? |
| 3. Responses |
| 3.1. Interested parties are requested to respond to this RFI with a white paper not to exceed 50 pages using 12-point Times New Roman font. Any supporting technical data and digital artifacts (to include model-based designs) provided will not count ag... |
| 3.2. Interested parties shall follow the instructions below regarding how to deliver the white paper response package content. RFI responses shall be organized into two separate sections. |
| 3.2.1. Section 1 of the white paper response shall provide administrative information to include the following as a minimum: |
| 3.2.1.1. Company name, mailing address, overnight delivery address (if different from mailing address), CAGE code, phone number, fax number, and both unclassified and SIPRNet e-mail of designated point of contact. Respondents are further requested to ... |
| 3.2.2. Section 2 of the white paper response shall address the recommended approaches to address the problem identified in paragraph 1 of this RFI and provide data as requested in paragraph 2. |
| 3.2.3. Responses should be marked, if applicable, with the appropriate controlled unclassified information (CUI) caveats, to include any ITAR restrictions. |
| 3.2.4. Responses should NOT include marketing information, commercial documentation, or product literature. |
| 3.3. Proprietary information, if any, MUST BE CLEARLY MARKED on the outside container and on the materials inside. The Government shall not be liable for or suffer any consequential damages for any proprietary information not properly identified. Plea... |
| 3.4. Respondents are advised that employees under contract with the Government may be used to administratively process submissions and provide technical support to the Government's Analysis of Alternatives requiring access to the contractor's propriet... |
| 4. Questions and Industry Discussion |
| 4.1. Questions regarding this announcement shall be submitted in writing via e-mail to the contracting officer, Mr. Christian Ryan (christian.ryan@us.af.mil), contract specialist Ms. Megan Porter (megan.porter.5@us.af.mil), and the technical coordinat... |
| 4.2. If warranted, government representatives may consolidate and disseminate general feedback to all respondents after white papers are submitted. Follow-on discussions with individual interested parties may be coordinated. The intent of any such dis... |
| 5. Future Work |
| 5.1. The government is evaluating an indefinite delivery, indefinite quantity (IDIQ) contract vehicle for potential future efforts (modeling, simulation, and analysis) associated with responses to this RFI (solicitation number FA8684-22-R-2006). Inter... |
File details come from the government source that posted it. Updated .