Sources Sought Response Template - 01 Oct 2025.xlsx
XLSX spreadsheet 26 KB Posted
- Solicitation number
- 243-25-157
About this file
This is a Sources Sought Response Template for Small Unmanned Aircraft Systems (sUAS) for the United States Marine Corps. The Navy's Program Executive Office for Unmanned Aviation and Strike Weapons (PEO U&W) is conducting market research to assess commercially available sUAS with First Person View (FPV) capabilities, targeting production quantities in the thousands. The template requires potential vendors to provide detailed information on cost, production capabilities, right to modify and repair, NDAA compliance, open standards, and technical specifications for unmanned aircraft systems.
Key submission requirements include providing unit costs for system quantities ranging from 500 to 10,000 units, detailing production capacity and delivery timelines, explaining supply chain security, and demonstrating compliance with 2020 and 2023 NDAA regulations and the American Security Drone Act. Vendors must submit responses electronically to specified Navy email addresses by 1600 EST, 60 days after the publish date, with the understanding that this is a market research tool and not a formal solicitation. The template covers critical evaluation areas such as technical interfaces, data rights, repair capabilities, and comprehensive system specifications including weight, speed, range, and payload capacities.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Government Responses 1.xlsx | XLSX spreadsheet | |
| Government Responses 1.xlsx | XLSX spreadsheet | |
| Government Responses 1.xlsx | XLSX spreadsheet | |
| Sources Sought Response Template - 01 Oct 2025.xlsx | XLSX spreadsheet | |
| Government Responses 1.xlsx | XLSX spreadsheet | |
| UAS System BOM Template - 01 Oct 2025.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Template
| DUE NLT: 1600 EST 60 days after Publish Date |
| Sources Sought Notification: Small Unmanned Aircraft Systems (sUAS) for the United States Marine Corps |
| Company: |
| Name of Contractor POC: |
| POC Email: |
| POC Phone Number: |
| Date of Submission: |
| INSTRUCTIONS | |
| Please provide as much information as possible to ensure your solution is evaluated properly. | |
| Your completed template must be submitted to heather.m.buckler.civ@us.navy.mil , kristen.w.ferro.civ@us.navy.mil NLT 1600 EST 60 days after publish date. | |
| As a reminder, responses to this Sources Sought Notification are for information and planning purposes only and does not constitute a proposal. | |
| All costs associated with submissions will be solely at the expense of the respondent. Please refer to Notice ID # 243-25-157 for additional ground rules: | |
| Table headers | Dark blue cells indicate table headers; these are not to be changed. |
| Row / column headers | Light grey cells indicate column headers; these are not to be changed. |
| Input cells | Light blue cells indicate inputs for interested parties to input responses. |
| COST | ||||
| Please enter the whole dollar amount in the input cells (e.g., $100,000), NOT $100K or $0.1M. | ||||
| Cost per Unit (USD) | Solution Name | [ENTER SOLUTION NAME HERE] | ||
| 500 systems | Enter unit cost for specified systems | |||
| 2,500 systems | Enter unit cost for specified systems | |||
| 5,000 systems | Enter unit cost for specified systems | |||
| 10,000 systems | Enter unit cost for specified systems | |||
| Please describe the key factors that influence your | ||||
| unit cost and provide a breakdown of the major cost components (e.g., materials, labor, overhead) | Enter methodology |
| PRODUCTION CAPABILITIES | ||
| Please enter the quantity of systems you can deliver to the United States Marine Corps by the date specified | ||
| Delivery Information | Solution Name | [ENTER SOLUTION NAME HERE] |
| Todays Date | Enter quantity you can deliver today. | |
| Today Date +30 days | Enter quantity you can deliver within 30 days. | |
| By what date can you deliver 500 systems? | Enter date you can deliver this quantity | |
| By what date can you deliver 2,500 systems? | Enter date you can deliver this quantity | |
| By what date can you deliver 5,000 systems? | Enter date you can deliver this quantity | |
| By what date can you deliver 10,000 systems? | Enter date you can deliver this quantity | |
| Where is your production facility located? | Enter location | |
| If you do not have a production line, are you willing to provide the Government with a technical data package that allows the Government or another third party to manufacture your design? | Yes, No, or provide explanation | |
| What is the maximum monthly production capacity of your facility? | Enter max # of units your facility can produce per month under current ops | |
| What steps would be required to further increase your production capacity to meet potential future demand? | Describe actions you could take (e.g., facility expansion, additional workforce, new equipment, supply chain adjustments) to increase monthly capacity. | |
| Do you have experience with high-volume manufacturing of similar systems? | If Yes, Provide examples, contract references, or production volumes if available | |
| Please describe your approach to ensuring the security and resilience of your supply chain, including measures to mitigate the risk of counterfeit components | Explain your supply chain security practices (e.g., approved vendor lists, quality assurance, traceability, certifications, testing, and anti-counterfeit measures). |
| RIGHT TO MODIFY AND RIGHT TO REPAIR | ||
| Please describe if your solution will support the following and identify the data rights your company will provide to the Government | ||
| Right to Modify | Can Marines modify the UAS system with a variety of third-party payloads, armaments, and munitions without vendor involvement? | Indicate whether your system supports independent third-party payload or munitions integration. Describe any limitations or restrictions. |
| What types of interfaces and documentation are provided to facilitate third-party payload integration? | List the physical, electrical, and software interfaces provided (e.g., NATO STANAG, open APIs). Identify supporting documentation available. | |
| Right to Repair | Does your solution enable Marines to perform repairs at the unit level, without requiring vendor support? | State whether unit-level repair is supported. Provide examples of repairs that can be performed without vendor involvement. |
| What level of technical documentation (e.g., maintenance manuals, schematics, troubleshooting guides) is provided to support organic repair efforts? | Specify the technical manuals and documentation provided, and indicate their level of detail (schematics, step-by-step guides, troubleshooting procedures). | |
| What training is available to Marines to enable them to perform repairs on your system? | Describe the training offered (e.g., classroom, online, hands-on) and identify the type/level of repair tasks Marines will be able to perform after completion. | |
| Are any specialized tools or equipment required to perform repairs on your system? If so, are these tools readily available and affordable? | List any specialized tools needed and clarify whether they are commercial off-the-shelf (COTS), available through standard supply chains, and approximate cost/availability. | |
| Do you allow the Government or other third parties to manufacture spare parts for your system? | State whether you permit government or third-party manufacturing of spares. Include any limitations or conditions. | |
| Data Rights | What level of data rights (Unlimited, Government Purpose, Specially Negotiated License, Restricted, etc.) are you offering to the Government with this solution? | Specify the level of data rights granted and any terms or conditions that apply. |
| Please specify the types of data that are covered by each data rights license (e.g., technical drawings, software source code, test data). | Identify which data sets fall under each license type (drawings, software, firmware, test reports, training materials, etc.). | |
| Are there any restrictions on the government's ability to share this data with other contractors or government agencies? | Indicate whether there are any restrictions on data-sharing and describe those restrictions clearly (e.g., limited to specific agencies, contractors, or programs). |
| NDAA Compliance | |
| Please provide NDAA compliance information | |
| Do your systems comply with Section 889 of the 2019 NDAA (and subsequent amendments) regarding prohibited drone components? | State whether your system is compliant with Section 889 and amendments. Provide details on how compliance is verified. |
| Please identify the country of origin for all critical components in your system (e.g., flight controller, GPS module, data link). | List each critical component and specify its country of origin. |
| Do you have a process in place to ensure ongoing compliance with NDAA regulations? | Describe your compliance process (e.g., supplier vetting, audits, documentation review) and how it ensures continued adherence to NDAA requirements. |
| Open Standards | ||
| Please provide Open Standards information | ||
| What communication protocols & versions does your system support (e.g., MAVLink)? | List all communication protocols and versions your system supports (e.g., MAVLink 2.0, proprietary protocols). | |
| What video transmission standards does your system use | ||
| (e.g., analog, HDZero, etc...)? | Specify the video transmission standards supported (e.g., analog, HDZero, Wi-Fi, proprietary digital links). | |
| Is your flight controller firmware open source? If so, which firmware is supported (e.g., Betaflight, EmuFlight)? | Indicate whether the firmware is open source. If yes, list the supported firmware(s) and version(s). |
| Technical Specifications | ||
| Please provide the technical specifications of your Air Vehicle | ||
| Technical Specifications | Max Gross Take Off Weight (MGTOW) | Enter the maximum gross takeoff weight in pounds (lbs). |
| Max Payload Weight | Enter the maximum payload capacity in pounds (lbs). | |
| Max Cruise Speed | Enter the maximum sustained cruise speed in miles per hour (mph). | |
| Max Dash Speed | Enter the maximum short-duration dash speed in miles per hour (mph). | |
| Max Speed | Enter the overall maximum achievable speed in miles per hour (mph). | |
| Max Altitude | Enter max operating altitude in feet above ground level (AGL) or mean sea level (MSL). | |
| Max Endurance | Enter the maximum endurance in hours and minutes (hh:mm). | |
| Max Range | Enter the maximum operational range in miles (mi). | |
| Dimensions and Weight of the Air Vehicle | Provide length, wingspan, height (inches or feet), empty weight (lbs) of the air vehicle. | |
| Total System Weight (AV, GCS, Battery, etc...) | Provide the combined total weight of the complete system (air vehicle, ground control station, power sources, and accessories) in pounds (lbs). | |
| Modular / Multi-Mission Payload Compatible? | Indicate whether the system supports multiple mission payloads. If yes, list compatible payload types. |
File details come from the government source that posted it. Updated .