Attachment 1 TRUAS RFI.pdf

Request for Information (RFI) for a Tactical Resupply Unmanned Aircraft System (TRUAS)

Solution

DISCLAIMER

THIS REQUEST FOR INFORMATION (RFI) IS FOR INFORMATIONAL PURPOSES ONLY. THIS IS NOT

A REQUEST FOR PROPOSAL; YET IS A MARKET RESEARCH TOOL TO DETERMINE POTENTIAL

FIRMS CAPABLE OF PROVIDING THE SUPPLIES DESCRIBED HEREIN PRIOR TO AN ISSUANCE OF A

REQUEST FOR PROPOSAL. THE GOVERNMENT IS NOT OBLIGATED TO AND WILL NOT PAY FOR

ANY INFORMATION RECEIVED FROM POTENTIAL SOURCES AS A RESULT OF THIS RFI. THIS DOES

NOT CONSTITUTE A SOLICITATION AND SHALL NOT BE CONSTRUED AS A COMMITMENT BY THE

GOVERNMENT OF ANY KIND. RESPONSES IN ANY FORM ARE NOT OFFERS AND THE

GOVERNMENT IS UNDER NO OBLIGATION TO AWARD A CONTRACT OR NON-FAR BASED

AGREEMENT (E.G. OTHER TRANSACTION) AS A RESULT OF THIS ANNOUNCEMENT. NO FUNDS

ARE AVAILABLE TO PAY FOR PREPARATION OF RESPONSES TO THIS ANNOUNCEMENT. ANY

INFORMATION SUBMITTED BY RESPONDENTS TO THIS TECHNICAL DESCRIPTION IS STRICTLY

VOLUNTARY. FAILURE TO SUBMIT A RESPONSE WILL NOT PREVENT A COMPANY FROM

PARTICIPATION IN ANY FUTURE COMPETETION RELATED TO PMA-263’s TACTICAL RESUPPLY

UNMANNED AIRCRAFT SYSTEM (TRUAS) PROGRAM.

1. INTRODUCTION

The Naval Air Systems Command (NAVAIR), Program Executive Office for Unmanned Aviation and Strike Weapons (PEO(U&W)), Navy and Marine Corps Small Tactical Unmanned Aircraft Systems Program Office (PMA-263), located at Patuxent River, MD, is conducting market research to identify potential sources capable of delivering a small to medium-sized Vertical Takeoff and Landing (VTOL) Tactical Resupply Unmanned Aircraft System (TRUAS) solution capable of achieving Top Level Requirements (TLR) for the United States Marine Corps. This system must meet operational focused on small unit logistics support across the last tactical mile in Expeditionary Advanced Base Operations (EABO) and Distributed Maritime Operations

(DMO).

NAVAIR is considering awarding an Other Transaction Agreement (OTA), pursuant to 10 U.S.C.

4022 “Authority of the Department of Defense to carry out certain prototype projects,” for TRUAS in FY2026.

2. Objective The objective of this RFI is to solicit technical feedback from industry regarding current or near-term mature solutions capable of meeting the following system attributes and key performance parameters outlined below.

Minimum Threshold Capabilities

Attribute Threshold/Objective

Payload 100 lbs for 40 Nautical Mile (NM) radius missions; 150 lbs for 10 NM missions.

Launch and Recovery

Vertical Take-off and Landing (VTOL) launch and recovery.

Speed Minimum 100 knots Indicated Airspeed (IAS).

Operational Altitude

4,500 ft Density Altitude (threshold); 8,000 ft (objective).

Endurance Combat radius 40 NM outbound + 40 NM return under load/empty condition.

Autonomy Autonomous low-altitude flight and obstacle avoidance.

Integrated sense-and-avoid for manned/unmanned deconfliction.

Autonomous mission profiles with programmable Lost Link, Return-to-Base (RTB), and contingency actions.

Capable of autonomous cargo delivery and return with payload release, loiter, and hover commands.

Cyber Survivability

Cyber survivable with Federal Information Processing Standards (FIPS) 140-3 Level 2 compliant encryption.

Maintainability Maintainability at the operator and field level with organic tools.

Multi-aircraft control

Single operator capable of controlling up to four (4) systems simultaneously.

Human Machine Interface

Fully compatible with USMC Unmanned Common Controller (UCC) and Marine Air Ground Task Force (MAGTF) Agile Network Gateway Link (MANGL).

Must support use of Digital Terrain Elevation Data (DTED), Tactical Awareness Kit (TAK)-based mission planning, and display live position on Common Operating Picture (COP) systems.

Command and Control

Onboard diagnostics, AI-assisted route optimization, and dynamic re-tasking capabilities.

Deployment Shipboard compatible for deployment from aviation-capable vessels and austere field environments.

Containerized for transport by Joint Light Tactical Vehicle (JLTV), four-person lift, and packaging within 4'x3'x2' volume (threshold).

The fully loaded container shall not exceed a weight of 150lbs.

Rapid deployability: Capable of operations within fifteen (15) minutes from transportation mode to airborne status.

Communications Capable of Beyond-Line-of-Sight (BLOS) operations with autonomous reroute and flight continuity

Regulatory Compliance

National Defense Authorization Act (NDAA) of 2024 Compliant with all applicable statutes

3. SUBMITTAL INFORMATION.

Interested persons may submit a Capability Statement package identifying their interest and capability to respond to the requirement or submit proposals. Only Capability Statements received on or before 15 calendar days after the posting date of this Notice will be considered by the Government. A determination by the Government not to compete this proposed contract action based upon responses to this Notice is solely within the discretion of the Government.

Capability Statements received will normally be considered solely for the purpose of determining whether to conduct a competitive procurement. Capability Statements submitted should be pertinent and specific in the technical/management/business area under consideration.

Provide detailed information in response to the questions listed below. Please answer them in the order in which they are asked:

1. What type of work has your company performed in the past in support of the same or similar requirement?

2. If your company is capable of delivery of three (3) prototype systems that meet the threshold requirements in FY28, please provide an explanation for how your company is able to feasibly achieve this requirement.

3. Please provide an overview of your company’s solution and technical approach with descriptions of major tasks/milestones to be performed. Identify pertinent Technology

Readiness Level (TRL), major technical risks, feasible risk mitigation efforts, and anticipated schedule.

Level Definition

TRL 9 Actual system proven through successful mission operation.

TRL 8 Actual system completed and qualified through test and demonstration.

TRL 7 System prototype demonstration in an operational environment.

TRL 6 System/subsystem model or prototype demonstration in a relevant environment.

TRL 5 Component and/or breadboard validation in a relevant environment.

TRL 4 Component and/or breadboard validation in a laboratory environment.

TRL 3 Analytical and experimental critical function and/or characteristic proof of concept.

TRL 2 Technology concept and/or application formulated.

TRL 1 Basic principles observed and reported.

Table 1: Technology Readiness Level (TRL) Definitions Table

Please provide details on the following technical attributes of your company’s potential solution.

If a specific attribute is estimated, unknown, or not applicable, clearly state the information.

Technical Attributes:

o System weight: AV only and total with payload o Max Gross Takeoff Weight (MGTOW) o AV and containerized system dimensions o Power source (battery, hybrid, fuel) o Launch and recovery method o Setup and turnaround time from stowed to launch-ready o Communications system Line of Sight/Beyond Line of Sight (LOS/BLOS, latency, data rate, encryption standards) o Navigation (GPS and Alt Position, Navigation, & Timing (PNT) methods) o Obstacle avoidance and airspace integration capabilities o Sensor payloads (if any) and sense-and-avoid details o Operating temperature, precipitation, wind conditions, storage limits o Altitude, range, endurance, cruise speed, max speed o Acoustic signature profile at 500’ and 1500’

Logistics and Maintainability:

o Description of system maintainability: Mean Time Between Failure (MTBF), Mean Time to Repair (MTTR), field-level repairs o Tools required: confirmation of compliance with Marine infantry toolkits o Spare part logistics, SL-3 kit contents, sustainment plan o Packaging and transportability methods (vehicle, ship, air, dismounted) o Required maintenance documentation, training package, simulation or virtual tools o Battery/fuel recharge/refuel requirements and times

Interoperability:

o Compatibility with Tactical Assault Kit (TAK), Universal Common Control (UCC), MAGTF Agile Network Gateway Link (MANGL), Common Aviation Command and Control System (CAC2S), Joint All-Domain Command and Control (JADC2), and

COP

o FAA and ICAO airspace integration capability o Air transponder configuration (Mode 5, ADS-B, etc.)

o C2 integration for joint and multinational operations

Manufacturing and Production:

o Current production capacity and timeline per order quantity (1, 10, 20, 50 units) o Facility locations and surge capacity o Prior fielding history (USG/FMS/commercial) o Interface Control Documentation (ICD) availability o NDAA 2024 compliance documentation

Cyber, E3, and Survivability:

o Cybersecurity features and self-zeroization o E3 compliance (MIL-STD 461G, 464C, DoDI 3222.03) o Electromagnetic survivability and Alt PNT integration o Low-Probability-of-Intercept/Detect communications o Kinetic and non-kinetic survivability features

4. Does your company require Government provided information, equipment, or material

(GPI/E/M) in order for your solution to meet the attributes and thresholds addressed in this notice? If so, please clarify the degree to which GPI/E/M will be requested or required.

5. Does your company have a Rough Order of Magnitude (ROM) cost estimate, anticipated

Period of Performance, and if applicable, anticipated cost sharing arrangement to meet the attributes and thresholds addressed in this notice? If so, please provide the information for

Government consideration.

6. Does your company have experience working with complex system of systems efforts, including multiple software packages, prototype weapons systems, engineering services and hardware/software integration of this nature? If so, please provide details.

7. Can or has your company managed a team of subcontractors before? If so, please cite contracts and teaming arrangement(s).

8. What specific technical skills does your company possess which will ensure its capability to meet the requirements identified above? If your company will be teaming or utilizing subcontractors, please include information regarding which work the subcontractor(s) will be responsible for and how the prime will determine the subcontractor is capable of accomplishing the work.

9. Would a fixed price type Contract or Other Transaction Agreement prevent the ability for your company to propose if phasing/spiral development or other element of modular contracting were provided?

10. Provide a statement including current small/large business status and company profile to include number of employees, annual revenue history, office locations, CAGE code, DUNS number, etc.

11. Respondents to this notice must also indicate whether they qualify as a Small, Small

Disadvantaged, Small Disadvantaged Veteran Owned Small Business, Women-Owned, 8(a), HUB Zone, Service-Disabled Veteran-Owned Small Business Concern, or Non-Traditional

Defense Contractor.

4. Responses

Interested parƟes are advised against submiƫng Capability Statements that merely mimic informaƟon in this RFI, provides brochure-like informaƟon, or provides general informaƟon.

Responses to this RFI are not to exceed 20 pages in length on 8.5X11 inch paper with one-inch margines and font no smaller than 10 points Times New Roman. The Government requests that respondents deliver responses electronically via email in MicrosoŌ Word or PDF format with proper data markings for unclassified and proprietary informaƟon no later than 15 calendar days aŌer the posƟng date of this RFI.

Classified material SHALL NOT be submiƩed. All submissions shall include this RFI Reference

Number, company name, company address, CAGE code, Unique EnƟty IdenƟfier (UEI) number, and a point of contact who is able to discuss the Capability Statement submiƩed. Point of

Contract informaƟon shall include name, posiƟon, phone number, and email address.

Acknowledgement of receipt will be provided. All informaƟon submiƩed will be adequately safeguarded from unauthorized disclosure in accordance with FAR 15.207. All submissions shall be clearly marked with the following capƟon: Controlled Unclassified InformaƟon (CUI), Releasable to Government Agencies for EvaluaƟon Purposes Only.

Responses that fail to comply with the above instrucƟons or present ideas not perƟnent to subject, may not be reviewed. All informaƟon received in response to this NoƟce that is marked proprietary will be handled accordingly. InformaƟon submiƩed in response to this NoƟce is submiƩed at no cost to the Government and will not be returned. The Government is under no obligaƟon to provide responses or comments to informaƟon received from interested persons but may request addiƟonal informaƟon following review. Note: If an interested person is a foreign concern or if a U.S. interested person has a team member or partner who is a foreign enƟty, adherence to all InternaƟonal Traffic and Arms RegulaƟons (ITAR) is required.

No telephone requests for addiƟonal informaƟon will be accepted. Please provide all responses via email to the addresses below.

Primary POC:

Joseph Perriello, Agreements Specialist Email: joseph.c.perriello.civ@us.navy.mil

Secondary POC:

Raymond Cannon, Agreements Officer Email: Raymond.c.cannon2.civ@us.navy.mil

5. Document Markings

All submissions must be clearly marked:

Controlled by: Department of the Navy Controlled by: NAVAIRSYSCOM PEO (U&W) PMA-263 CUI Category[ies]: Controlled Technical Information / Export Controlled Distribution/Dissemination Control: Distribution C FEDCON POC: KEITH TAYLOR, keith.w.taylor1.civ@us.navy.mil

Proprietary data will be handled in accordance with FAR 15.207. Foreign participants must adhere to ITAR regulations.