RFI_A2E_Whitepapers.pdf

Adaptive Airborne Enterprise (A2E) AltPNT White Paper

This Request for Information (RFI) is for market research purposes ONLY.

The Department of the Air Force (DAF) is seeking capability information for the subject RFI from all interested parties. In accordance with FAR 15.201(e), RFI responses are not offers and cannot be accepted by the government to form a binding contract. This RFI is issued solely for information and planning purposes and does not constitute a request for proposals. Respondents will not be reimbursed for costs incurred in responding to this RFI.

Note: DAF is neither obligated to acknowledge receipt of the information received nor to provide feedback to responses. Based on the responses submitted, DAF may choose, at its own discretion, to reach out to individual respondents for further clarifying information.

Requirement: Early Access Middleware Integration Partnership

The Air Force Special Operations Command (AFSOC) Adaptive Airborne Enterprise (A2E) team is seeking technical partners to evaluate and provide feedback on the drone middleware platform called the Golden Horde Autonomy Architecture (GHAA) from February to April 2025, before launching a larger Autonomy Consortium. This initial phase focuses on refining our middleware interfaces, SDKs, and establishing baseline autonomy capabilities.

We request a brief whitepaper addressing:

1. Technical approach for:

a. Middleware evaluation (interface requirements, SDK improvements, integration feedback)

b. Integration and testing of perception, motion planning, and control modules

c. Integration of proprietary alternative position, navigation, and timing (altPNT) capabilities

d. Testing platforms: simulation or hardware (desired)

2. Integration cost estimate

3. Key technical personnel and relevant experience

The focus is on GPS-denied PNT capabilities, with emphasis on perception, planning, and control integration. Please highlight any experience with ROS2 (or related middleware), containerization, and developing visual navigation algorithms.

Format: Please use the attached template and follow these formatting requirements:

• Times New Roman, 12pt font

• Single Spaced

• Maximum 5 pages

• PDF format

Business Sensitive, Proprietary, Or Otherwise Confidential Information:

Responses must be marked as proprietary or restricted data. Responses will not be shared with any other respondent. Respondents will not be notified of the results of the market research. Not responding to this RFI does not preclude submitting a proposal in response to any future solicitation.

Response Date & Time: Submissions are due Friday, 14 February 2025, 1600ET. Whitepapers should be submitted to the following POCs: Kristina Botelho, email kristina.botelho@us.af.mil;

John Alora, email: john.alora.1@us.af.mil; & Athena Chang, email: athena.chang.1@us.af.mil

Please label your white paper as follows: CompanyName_A2E_RFIWhitepaper mailto:kristina.botelho@us.af.mil mailto:john.alora.1@us.af.mil mailto:athena.chang.1@us.af.mil

Task/Project Title

White Paper Submitted to Department of the Air Force (DAF) – Stanford AI Studio

Company Logo (not required)

Prepared By

Company Name Technical POC Name

Address Email address Phone number

Webpage Cage Code/UEI

Date Date of Submission

The main headers for the template are in Black. The instructions and rationale for each item in the templates are in blue and can be erased as the template is completed. Please keep “white papers” succinct and to the point, preferred page count is no more than 5 pages (excluding the cover page).

1. Company Information

Provide the following information: Company Name, CAGE code (if available), Company Size (number of employees) and NAICS codes. Include a BRIEF synopsis outlining the firm’s capabilities and experience.

2. Task Objectives Describe your approach to evaluating and improving the Golden Horde Autonomy Architecture (our middleware platform) between Feb-Apr 2025, including integration goals for altPNT capabilities and plans for SDK/interface refinement.

3. Technical Approach Detail your integration strategy, focusing on:

• Middleware evaluation methods

• Integration of perception, planning, and control modules

• altPNT implementation

• Testing approach (simulation/hardware)

4. Deliverables

Provide intended deliverables by late March 2025 (i.e. Test Plan, Test Results, Drawings, Tech Data Package, Specifications, Prototype, etc). What will this effort entail? How will this effort address the needs outlined in the previous sections?

5. Rough Order of Magnitude (ROM) Provide estimated total cost for the effort. This includes:

• Engineering hours

• Hardware (if applicable)

• Testing resources

• Other relevant costs

6. Schedule

Provide a draft timeline of effort to include major activities/tasks and milestones for the Feb- Apr 2025 period.

7. Technical Team

List key engineering personnel, their roles, and relevant experience in ROS2 (or similar middleware), containerization, and developing visual navigation algorithms.

8. Disclaimer(s) USE AND DISCLOSURE OF DATA – “This white paper includes data that shall not be disclosed outside the Government and shall not be duplicated, used, or disclosed – in whole or in part – for any purpose other than to evaluate Return on Investment of effort”

The Government does not intend to award a contract on the basis of this submittal. The information will be used for planning purposes, for the purpose of collecting market research, solely for informational, planning, and identification of capable sources.