AoI UAS Test Support Services.docx

Area of Interest (AoI): UAS Test Support Services Agency: Department of the Army Program: Vehicle Protection Systems (VPS)

1.0 General Information

1.1 Introduction

The Ground Vehicle Systems Center (GVSC) and Project Manager Vehicle Protection Systems (PdM VPS) are seeking an industry partner or contractor team to provide Unmanned Aircraft Systems (UAS) equipment, flight operations/piloting, and field test support for multiple upcoming counter-UAS (C-UAS) test events.

During these events, threat-representative UAS will execute complex, coordinated flight patterns to evaluate the detection, tracking, and classification capabilities of both stationary and On-The-Move (OTM) C-UAS sensors. A primary test objective is to assess how accurately the C-UAS sensors can determine the bearing and range to an incoming UAS.

Therefore, the respondent’s solution shall continuously determine and record 3D spatial coordinates (latitude, longitude, and altitude via Real-Time Kinematic (RTK) or equivalent technology), and Global Positioning System (GPS) synchronized timestamps, for both their UAS and the System Under Test (SUT).

This AoI establishes broad UAS performance envelopes (size, speed, endurance, flight-mode, payload, etc.) required to guide industry responses. To ensure a blind, realistic test environment, detailed test-specific threat configurations, including specific airframes, quantities, radar/optical signatures, communications protocols, detailed flight profiles, and other characteristics that could enable pre-event sensor optimization, will not be provided to sensor vendors before the event. Respondents shall not disclose non-public, Government-provided test-specific configuration information without prior written Government authorization.

Interested parties are highly encouraged to review the Army Contracting Command–Detroit Arsenal (ACC-DTA) Commercial Solutions Opening (CSO) special posting W912CH-26-S-0001 at ACC-DTA Commercial Solutions opening (CSO) for complete details on the submission and evaluation process.

This CSO AoI seeks to solicit innovative solutions that meet the operational and technical objectives detailed in Section 1.3. The term “innovative” is defined in accordance with 10 U.S.C. § 3458 as any technology, process, or method, including research and development, that is new as of the date of proposal submission, or any new application of an existing technology, process, or method as of the proposal date.

The Contracting/Agreements Officer is not obligated to extend a request for Commercial Solution Proposal (CSP) or make an award as a result of this CSO AoI; all awards/agreements are subject to the availability of funds and successful negotiations. This CSO AoI is not an authorization to begin performance, and in no way obligates the Government for any costs incurred by the Offeror associated with developing a response. Prior to commencement of any activities associated with performance under this CSO AoI, the Government will issue a written directive or contractual document signed by the Contracting/Agreements Officer with appropriate consideration established. The Government reserves the right to modify the requirements of this CSO AoI.

The authority to issue this CSO AoI is derived from W912CH-26-S-0001, dated 08 January 2026. The CSO authority is 10 U.S.C. § 3458 (Authority to acquire innovative commercial products and commercial services using general solicitation competitive procedures) and DFARS 212.70 (Defense Commercial Solutions Opening).

1.2 Phase 1: Content of Solution Brief

The written solution brief shall address the following:

Vendors are required to submit CSO Phase 1 solution briefs in accordance with ACC-DTA CSO, W912CH-26-S-0001, Section 3.2.1.

Describe your technology and its relevance to Section 1.3 below.

1.3 Technical Requirements

Threat-Representative UAS Hardware Requirements The requested support encompasses both hardware assets and operational field services. The following baseline specifications identify the capabilities respondents must address in their solution brief:

· Airframe Configurations

· The Government is interested in solutions that offer UAS in multiple airframe configurations, including multirotor, fixed-wing, and other novel airframe configurations representative of current and emerging worldwide threat UAS.

· Target Categories

· Small Group 1 UAS: approximately 2 pounds gross weight; cruise speed of up to 25 knots; flight duration of 25 minutes or more; and payload capacity of 1.5 pounds or more.

· Medium Group 1 UAS: approximately 10 pounds gross weight; cruise speed of up to 100 knots or more; flight duration of 30 minutes or more; and payload capacity of 5 pounds or more.

· Group 2 fixed-wing UAS: approximately 20–40 pounds gross weight; cruise speed of 50 knots or more; flight duration of 30 minutes or more; and payload to be specified by respondent.

· Common desired UAS capabilities

· Guidance & Navigation Modes: Autonomous waypoint navigation, First-Person View (FPV), and manual flight mode.

· Communications & RTK: Telemetry, logging, and communications out to 10 kilometers.

· Operating Environment: Respondents must account for Non-Line of Sight conditions. The 10 km range requirement must be maintained in environments containing natural terrain masking, including hills, foliage, and varying elevations typical of tactical test ranges. Respondents shall detail their approach to maintaining link margin in these conditions.

· Video Feed: For applicable airframes, the video feed from the UAS shall be transmitted with a latency not exceeding 50 milliseconds for streaming and recording at the command trailer. Video transmission shall utilize low-latency, visually lossless compression.

· Payload Integration: General Purpose Input/Output (GPIO) or equivalent interface to support the physical integration of custom payloads which are controllable via wireless signal, where applicable. Latency for payload control and status reporting must not exceed 50 milliseconds.

· Logging: The UAS shall possess means of continuously logging all peripheral data (video feeds, RTK signals, payload status, etc.) locally.

Ground Support, Launch, and Ranch Integration Respondents shall provide turnkey ground support infrastructure capable of sustaining simultaneous operations:

· Dual Concurrent Launch Locations: Capability to support two physically separated, concurrent launch locations. Respondents shall identify the proposed pilot teams, UAS assets, ground-control stations, communications equipment, and positioning equipment to support two concurrent launch locations.

· Live Telemetry Interface: Provide live flight feedback to the command trailer. A refresh rate of 1 Hertz is acceptable for this live telemetry display. (Note: This is distinct from the continuous data logging and low latency requirement for video and payload control).

· Communications Architecture & Spectrum Support: Describe proposed command-and-control, video, and RTK-correction communications; required ground equipment and communications, expected range limitations; spectrum requirements; command-trailer interface requirements, and other communications dependencies or constraints.

· Government-Furnished Equipment & Facilities: Identify all assumed Government-furnished support and dependencies, including spectrum or range authorization, power, launch and recovery areas, workspace, network or command-trailer interfaces, positioning infrastructure, and other required Government support.

· Auxiliary Support Equipment: Identify additional hardware required to execute the proposed solution

Position, Timing, and Data Collection Provide a proposed solution for obtaining and recording GPS-defined geographic position accuracy of 5 cm or better for threat-representative UAS and the SUT.

· Record in UAS flight logs:

· Position and timing data: data at 20 Hertz or greater, latitude, longitude, altitude, and GPS Atomic Clock-synchronized timestamp for each data point UAS and SUT data point.

· System-status data: GPIO status, velocity, speed, acceleration, and RTK/GPS solution status or equivalent position-quality indicator.

· Provide, with your submission, a sample flight-log data file in your proposed delivery format. The Comma-Separated Values (CSV) format is preferred, the ULog format is acceptable. Other formats will require Government approval.

· Retrieve, validate, and deliver UAS flight logs to the Government by the conclusion of each flight day using a Government-approved format and delivery medium.

This AoI is a public announcement. Information provided in this AoI is releasable to the public. It is anticipated that performance under this program may require access to Official Use Only (OUO) and other non-public Government information. All respondents and participating personnel shall protect and safeguard all non-public, Government-provided information. Respondents shall not disclose any non-public information, including but not limited to test-specific threat profiles, SUT telemetry, technical performance data, test and evaluation results, or any material marked as sensitive or proprietary by the Government, to any third party without the express prior written consent of the cognizant Contracting Officer. Unauthorized disclosure may result in immediate disqualification, termination for default, and referral for administrative, civil, or criminal penalties as prescribed by federal law.

Data Rights and Intellectual Property The Government is expecting rights in data in accordance with DFARS 252.227-7989, 252.227-7990, and 227.7202-3. Pursuant to DFARS 252.227-7989, the Government shall receive the following rights in data generated under any associated contractual document:

· Unlimited Rights in Test Data Deliverables: The Government shall receive Unlimited Rights in all Time-Space-Position Information data, flight logs, position and timing coordinates, sensor recordings, video footage captured during range execution, system status logs, payload event logs, and formal evaluation reports delivered under this effort. "Unlimited Rights" authorizes the Government to use, duplicate, release, perform, display, or disclose these technical data in whole or in part, in any manner and for any purpose whatsoever, and to authorize others (including other DoD agencies and technical support contractors) to do so.

· Proprietary Hardware and Software: The contractor retains ownership and intellectual property rights in their pre-existing proprietary commercial UAS airframes, firmware, autopilot software algorithms, and Ground Control Station (GCS) software. The contractor grants the Government a perpetual, non-exclusive, royalty-free license to access and utilize interface software, Application Programming Interfaces (APIs), and data dictionary documentation solely for internal Government test integration and analysis.

2.0 Requested Services & Execution Timeline

· Pre-Event Support

· Events:

· Kickoff meeting

· Periodic status meetings

· Test-site visit

· Activities:

· Review design and test-event planning

· Provide sample flight-log data

· Flight-plan development

· Constraint Identification;

· Identify communications, spectrum, site, operational, and other constraints affecting the proposed solution

· On-Range Event Support

· Flight Operations Crews: Provide qualified UAS personnel (pilot teams, maintainers, and other support personnel) to independently sustain dual concurrent launch sites.

· Daily Delivery: Retrieve, validate, and deliver UAS flight logs at the conclusion of each flight day.

· Asset Capacity: Identify the maximum number of UAS that can be concurrently operated and supported during the event.

· On-Site Spares: Maintain an on-site supply of UAS common replaceable parts (including additional airframes, batteries, rotors, and integration hardware) sufficient to sustain the planned testing period.

· On-Site Repair: Provide on-range maintenance and repair capabilities. Maintainers must possess the tools and expertise to conduct field repairs immediately on the range to minimize UAS downtime and prevent test delays.

· Post-Event Support:

· De-mobilization: Pack and ship equipment.

· Post-Flight Data Reconciliation: Provide post-event support for questions regarding logs and related data, not to exceed 20 labor hours.

3.0 Submission Instructions

Vendors are required to submit CSO Phase 1 solution briefs, including a pricing Rough Order of Magnitude) ROM, in accordance with ACC-DTA CSO, W912CH-26-S-0001, Section 3.2. Solution briefs received after the specified due date and time will be discarded and not be evaluated by the Government.

Submissions shall identify any restrictions on the Government’s rights (e.g. data rights) in using/disclosing/reproducing/modifying technical data, computer software, and non-technical data (e.g. business/financial/administrative data) involved in the effort.

Cost & Pricing Information Respondents shall provide estimated Firm-Fixed-Price pricing for the following:

· Hardware Acquisition & Lease:

· Unit purchase pricing for each proposed UAS configuration and associated support equipment, spares, software licensing.

· Optional lease/rental rates for hardware packages on a per-event or per-day basis.

· Operational Support:

· Firm-fixed daily or weekly field service crew rates.

· Mobilization, travel, per diem, and logistics transportation costs.

· Optional Capabilities (Separately Priced):

· Identify capabilities that expand threat-representative UAS capacity, such as additional airframe types, payload configuration options, greater concurrent-UAS capacity, or rapid UAS reconfiguration.

· Identify capabilities that expand event support, such as additional launch locations, data-processing support, or other capabilities that add value to Government test events.

· Assumptions & Availability:

· Respondents shall outline all estimating/pricing assumptions, delivery/component lead times, and availability assumptions.

AoI Open Period:

To be considered for fiscal year 2027 test events, solution briefs are due by 16 November, 2026. by 4:00pm ET. This AoI shall remain open for potential improvements for future, as-yet unscheduled test events.

Points of Contact (PoC) Solution briefs and any questions should be submitted to the following PoCs:

Contract Specialist: Lauren Wagner, lauren.e.wagner10.civ@army.mil Contracting Officer: Jennifer Harris, jennifer.l.harris194.civ@army.mil