Request for Information (RFI) for Long Range Tactical (LRT) Unmanned Aircraft Systems (UAS), PMA-263, International IPT
Source Record
DISCLAIMER THIS REQUEST FOR INFORMATION (RFI) IS FOR INFORMATIONAL PURPOSES ONLY. THIS IS NOT A REQUEST FOR PROPOSAL. IT IS A MARKET RESEARCH TOOL BEING USED TO DETERMINE POTENTIAL FIRMS CAPABLE OF PROVIDING THE SUPPLIES DESCRIBED HEREIN PRIOR TO DETERMINING THE METHOD OF ACQUISITION AND 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. RESPONSES IN ANY FORM ARE NOT OFFERS AND THE GOVERNMENT IS UNDER NO OBLIGATION TO AWARD A CONTRACT 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 THE LRT UNMANNED PROGRAM. NO TELEPHONE RESPONSES WILL BE ACCEPTED. 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) at Patuxent River, MD is seeking industry input to identify potential solutions for a UAS to be used by an international partner for Maritime Domain Awareness (MDA) and search and rescue operations remaining on station for up to 48 hours. The system needs to be able to operate in static rain environments up to 1 inch per hour, conduct wide area surveillance, cued response with localized search, vessel classification, identification and tracking. The system should be ready to use, as delivered, with minimal logistics, training, and other support. The system should provide real-time full motion video via electro-optical and infrared sensors (EO/IR), with the ability to detect and monitor large and small objects in the water (i.e. small vessels, people) distinguish between vessel types (i.e. fishing, merchant, tanker, state). The Air Vehicles (AV) should be capable of autonomous or safe manual launch and recovery, independent of runways. The Ground Control Station (GCS) should be man-portable and consist of the necessary equipment to monitor the sensor(s) position and status, control its movement and view its video. 2. Objective PEO (U&W), PMA-263 is specifically interested in systems with the following characteristics: Small Unmanned Aircraft System ((Air Vehicle (AV) MGTOW (with payload) < 55 lbs.)) Maximum Four-person set-up Minimum line-of-sight range of 60 kilometers (one way) Minimum endurance 48 hours Real-time Full Motion Video (FMV) via dual mode gimbaled EO/IR payload Multiple modular payload capability (i.e. allows for a secondary payload, including 3rd party payloads) Modular and open architecture Ability to operate in multiple weather/environmental conditions TRL 8 or higher: Adequate maturity for immediate production, delivery, fielding and deployment. National Defense Authorization Act (NDAA) 2024 compliant 3. Requested Information The responder is requested to provide detailed information in response to the following: Identify the following technical attributes of the potential solution. If a specific attribute is estimated or unknown, so state: System Characteristics AV weight without payload AV weight with payload AV Max Gross Take-Off Weight AV dimensions (assembled) Size and weight of total system packed for transport AV Guidance (GPS, GPS Denied, etc.) GCS dimensions and weight with antenna (assembled) Power source(s) Set up time (time required to go from packed to system airborne) Payload Available payload weight Sensor type Sensor detection/identification performance (National Image Interpretability Rating if applicable) Environmental Conditions Temperature limits Precipitation limits Wind limits Maritime environmental limits Water immersion limits Environmental conditions for storage Performance Limits Altitude limits (above ground and pressure altitude) Maximum range (maximum range at which the system can operate assuming line-of-sight) Maximum endurance (maximum time the AV can remain airborne under optimal conditions at sea level) Maximum speed of the air vehicle Optimal cruise speed Acoustic signature at 500� and 1500� Provide detailed information in response to the questions listed below. Please answer them in the order in which they are asked: What is the software operating system? Open Architecture? How does the system navigate? Is the system capable of navigation without Global Positioning Unit (GPS)? If so, please provide a description. Does the system use Selective Availability Anti-Spoofing Module or M-Code GPS? Does your system have an organic obstacle/threat avoidance capability? What are the different types of flight modes and mission control characteristics used by the system? (Manual, autonomous, waypoints, loiters, hover and stare, etc.) Does your system incorporate autonomy via Artificial Intelligence control, operation, decision-making, and machine learning? What safety features (i.e. lost link, lost GPS) are built into the system? Can the air vehicle be launched and/or recovered from a moving ship? How is the system launched/recovered? Can the air vehicle be safely landed on water? Is the system water recoverable? What is the total time for system set-up and launch? Is there any launch or recovery equipment required? If so, please provide a description. Does the system have a precision recovery capability? What mapping software does the system use (google maps, Falcon View, open source, etc.) and does it have Digital Terrain Elevation Data (DTED)? Does the system use standard Department of Defense (DoD) mapping and imagery? What are your system requirements to load maps and Digital Terrain Elevation Data (DTED)? Is an internet connection required to obtain map data? How does the GCS communicate with the AV? Describe the data link used including waveform, operational frequency band, analog or digital, and encryption capabilities. Can the AV operate without comms to the GCS after uploading flight profile and launch? Is the system capable of simultaneous multiple AV operations from a single GCS? Does your system have the capability to interface with DoD common operating picture or tactical networks (TAK, ATAK, ROS, RAS-G IOP, etc.)? Is the air vehicle capable of operation via the USMC MAGTAB controller? Is your product NDAA compliant? If no, what steps are being taken to ensure compliance? If yes, provide supporting documentation. How do you track your suppliers/subsystems for compliance? How and where is the data (video, pictures, and flight logs) stored and protected? How is data processed? Can third party software be processed on the AV? Are you willing to release full Interface Control Document for avionics, payload and battery interfaces? What payloads are currently available, in development, planned, compatible and/or integrated with the system ((from original equipment manufacturer (OEM) or third party))? What other unique capabilities are available with the system that may enhance mission performance? What type of batteries are used? How are batteries recharged and how much time is required to return to full charge following a maximum endurance flight? Do the batteries have a certification, i.e. NOSSA, UL? If LRT will use fuel cells, describe: Type/Class Certifications Environmental Considerations Risks associated with normal operations and mitigation Handling/Storage/Transportation requirements Point of Production Capability What is your experience with developing Small Unmanned Aircraft System products? How many units have been sold/fielded to date? If able, please identify user(s) of the identified solution (Military/Industry/FMS). What is the production lead-time; including any production, capacity, and delivery constraints based on order quantities of 1, 10