Drone Marketplace Onboarding of Group 3 UAS

1. Background

The U.S. Army Contracting Command – Redstone Arsenal (ACC-RSA) is issuing this Call for Solutions against Commercial Solutions Opening (CSO) W58RGZ-26-S-C001 under the authority of 10 U.S.C. § 3458. This Call will competitively acquire and onboard innovative commercial Uncrewed Aircraft Systems (UAS) in the Group 3 classification onto the Drone Marketplace.

A Group 3 UAS is defined by the Department of Defense as an aircraft that weighs between 55 pounds and 1,320 pounds (maximum gross takeoff weight), operates at altitudes up to 18,000 feet above mean sea level, and typically flies at speeds less than 250 knots.

This is intended to be an open and enduring call to continuously survey and onboard new technology for a period not to exceed five (5) years. The Government reserves the right to alter or cancel this call at any time.

The UAS Marketplace is a strategic initiative designed to scale the industrial base and accelerate the delivery of UAS capabilities by empowering Soldiers with the freedom to choose the equipment that best meets their mission needs. This approach marks a significant pivot from traditional acquisition models to a dynamic, free-market concept.

The primary goal of this Call is to identify and assess innovative Group 3 UAS solutions for placement on the UAS Marketplace. The process is designed to evaluate systems and onboard them to the UAS Marketplace, culminating in one of two levels of procurement readiness: Provisional or Cleared.

It is critical for all offerors to understand that this Call’s primary purpose is to establish a pool of qualified vendors available for purchase on the UAS Marketplace. The onboarding process and establishment of a Basic Ordering Agreement (BOA) does not constitute a production contract or guarantee any future orders. All procurement will be initiated by PM UAS and/or U.S. Army end-users based on their specific mission requirements and the availability of funds.

2. Problem Statement

The character and pace of modern warfare are being redefined by the rapid proliferation and innovation of UAS. Our near-peer competitors are deploying these capabilities with a speed and scale that directly threatens our technological advantage at the tactical edge. Recent Department of War (DoW) guidance directs a shift to a wartime footing, demanding that we accelerate acquisition timelines and scale the industrial base to meet this evolving threat. The current acquisition process is not structured to keep pace, creating a critical capability gap and putting Soldiers at risk against a technologically adaptive adversary.

To address this urgent need, the Army must rapidly identify, assess, and procure innovative, commercially available Group 3 UAS that are ready to field now. This Call seeks to fill critical UAS capability gaps by leveraging the commercial drone market’s dynamism and innovation. The objective is to move away from traditional, lengthy development cycles and onboard mature, effective, and immediately procurable solutions into the UAS Marketplace. This approach will empower the warfighter with the cutting-edge capability required to dominate the modern battlefield and restore our decisive advantage.

3. Technical Attributes

A detailed description of the required and desired technical attributes for the UAS solutions is provided in the SOO, included as Attachment 1 to this Call. Offerors must refer to the SOO for a comprehensive understanding of the Government’s technical objectives. In general, the Government is seeking innovative, commercially available Group 3 UAS platforms that are production-ready or at least a least a Technology Readiness Level (TRL) of 7 and capable of performing missions such as Reconnaissance, Surveillance, and Target Acquisition (RSTA), electronic warfare, communications relay, and cargo delivery. The Government will accept submissions for solutions with a TRL of less than 7 with a demonstrated plan to achieve TRL 7. The Government may request to include lower TRL systems in demonstration, exercise, or other testing events to assist industry achieving a higher TRL.

4. Award Information

4.1 Authority and Instrument Award

This Call is issued under the authority of Commercial Solutions Opening (CSO) procedures detailed within the Uncrewed Aircraft System Marketplace Commercial Solutions Opening W58RGZ-26-S-C001, found at SAM.gov Opportunity Link

In accordance with 10 US Code 3458, use of a CSO is considered a competitive procedure. The Government intends to establish one or more Firm-Fixed-Price BOAs as a result of this Call. A BOA is not a contract and does not obligate any funds or guarantee any future orders. It is a written instrument of understanding that establishes the terms and conditions for potential future orders. All orders placed against the BOA are subject to the availability of funds. While the BOA will be the primary acquisition vehicle, procurements resulting from this Call may be made through various instruments to include but not limited to already established other Government agency contracts or establish alternate contract vehicles that may include Other Transactions (Ots) or new, negotiated FAR-based contracts.

4.2 Offeror Eligibility Requirements

To be eligible for the UAS Marketplace, offerors must meet all of the following requirements:

• All proposed Unmanned Aircraft Systems must be fully compliant with Section 848 of the National Defense Authorization Act (NDAA) for Fiscal Year 2020 (and associated NDAA sections), which prohibits the procurement and use of UAS, and their critical flight components manufactured in covered foreign countries, including the People’s Republic of China. Offerors must be prepared to provide a complete Bill of Materials (BOM) or Software Bill of Materials (SBOM) and support supply chain verification activities to prove compliance.
• Be considered a responsible contractor in accordance with FAR Part 9.1.
• Possess a Unique Entity ID (UEI) and have an active and approved registration in the System for Award Management (SAM.gov).
• Have an approved Commercial and Government Entity (CAGE) code.
• Have a current NIST SP 800-171 DoW assessment completed and posted in the Supplier Performance Risk System (SPRS) in accordance with DFARS 252.204-7019.
• Meet all cybersecurity requirements stipulated in this solicitation, which may include a specific Cybersecurity Maturity Model Certification (CMMC) level and compliance specified in the resulting BOA or orders in accordance with DFARS Clause 252.204-7012 for the protection of Controlled Unclassified Information.
• Disclose any actual or potential Organizational Conflicts of Interest (OCIs) to the Contracting Officer.
• Be registered in the prescribed government invoicing system (e.g., Wide Area Workflow).

4.3 Government Rights and Disclaimers

UAS Marketplace Onboarding Decision: The Government reserves the right to make multiple awards, a single award, or no award as a result of this Call.

Binding Authority: Only a warranted Contracting or Agreements Officer has the authority to enter, modify, or execute a binding instrument on behalf of the United States Government.

Cancellation: The Government reserves the right to cancel this Call, either before or after the closing date. If the Call is canceled, the Government has no obligation to reimburse an offeror for any proposal preparation costs.

Standard Terms: The terms and conditions of any resulting BOA will be based on FAR Part 12. Offerors are encouraged to review FAR 52.212-4 and 52.212-5. The offeror will be required to review and accept additional UAS Marketplace specific terms and conditions.

4.4 Submission Updates and Revisions

Offerors are responsible for maintaining a current, complete, and accurate submission package. Throughout the open period of this CSO, offerors may submit revised documentation to update their submission to correct inadvertent errors or address feedback from the Government. The formal acceptance of any updates into the official evaluation package, however, remains at the sole discretion of the Government. All evaluations will be based on the latest submission officially accepted by the Government at the time of review.

5. Solution Submission Requirements

5.1 Overview of Submission Steps

The Government will utilize a three-step process to evaluate submissions. An offeror must successfully pass each step to be considered for the next. Offerors who successfully complete the Initial Capability Assessment (Step 1) will be eligible for onboarding and will proceed to Step 2 for further verification and security assessment. Upon determination of full eligibility, the Government will invite the offeror to submit a Full Proposal (Step 3) to establish a FAR Part 12-based BOA.

An offeror who does not successfully pass a step will not be disqualified from consideration. The Government may, at its discretion, provide feedback on the submission’s deficiencies, and the offeror may revise and resubmit their materials for re-evaluation in accordance with the continuous, rolling basis of this CSO.

Crucially, the establishment of a BOA does not constitute a purchase or a guarantee of future orders. The BOA serves only as the contractual framework that makes the UAS available for purchase. If a government user determines that a specific UAS meets their unique operational needs, they may initiate an order against the established BOA via the UAS Marketplace. The Government makes no commitment to the volume or frequency of orders.

5.2 Step 1 – Initial Capability Assessment

As the foundational step, interested offerors must submit an Initial Acceptance Packet (IAP). The IAP is a consolidated packet that provides an initial overview of the vendor and the proposed solution and includes:

• Vendor Information: Company and contact details, summary of qualifications, certifications, and legal compliance, and past or current DoW and commercial contracts.
• Product Information: Detailed description of the product, including its classification, its intended use, its compliance with relevant regulations, and interoperability and integration with current Army systems and standards.
• System-Level Technical Data on Platform Information, Command & Control (C2) Datalinks, and Payloads.
• Comprehensive, vendor-provided data on the platform’s performance, physical characteristics, and transportation logistics.
• Detailed specifications for the system’s Position, Navigation, & Timing (PNT) capabilities, air vehicle datalinks, and ground control systems.
• In-depth technical details for all compatible payloads to include spectral, noise, and embedded Automatic Target Recognition (ATR) characteristics.
• Software and Services Information: Complete details on the software system - including its architecture, hardware and operating system compatibility, dependencies, and licensing model - along with a comprehensive overview of offered services, such as system integration, testing, simulation, training, and maintenance. Include current systems or architectures with which the software has already been integrated.
• Supporting Documentation (Attachments): A set of clearly labeled and organized documents to supplement their IAP. These are categorized as Required, which are mandatory for the IAP to be considered complete, and Desired, which are not mandatory but significantly strengthen a submission by providing additional context and evidence of capability.

Upon successful evaluation of the IAP, offerors may be invited to conduct a system demonstration at a location selected by the Government, or in a virtual environment. To facilitate this event, the Government will issue a coordination packet and schedule a technical interchange meeting with the offeror prior to the demonstration. Demonstration locations may have specific insurance requirements that require vendors to provide a Certificate of Liability Insurance (COLI) that includes designated entities as additional insured. Specific details will be provided when demonstrations are scheduled. Instructions for submission of the IAP are on the UAS Marketplace storefront, UAS Marketplace Storefront, (https://uasmarketplace.army.mil/). The instructions provided on the UAS Marketplace storefront are for guidance. In the event of a conflict, the requirements of this Call for Solutions document shall take precedence.

5.3 Step 2 Submission: Continuous Verification Submission

*Note to Offerors:

The Verification Activities (VA) described in this section are not a determining factor for Marketplace onboarding. The primary purpose of the VA is to generate comprehensive, verified system-relevant data that will be published on the storefront. This data serves to inform government buyer decisions and build confidence in the Marketplace offerings. The VA is a continuous process that occurs throughout both Step 2 and Step 3 to create a robust, thoroughly vetted profile for systems.

Following the foundational submission of the IAP, offerors shall further substantiate their system’s capabilities through the Verification Activities Questionnaire (VAQ). Whereas the IAP serves as the vendor-provided overview for initial consideration, the VAQ initiates the in-depth system verification process. The VAQ submission requires offerors to provide detailed, verifiable evidence that substantiates the claims and specifications outlined in their IAP. While the requested information categories mirror those of the IAP, the VAQ serves as a more comprehensive evaluation of each category, that requests more rigorous evidence. This includes, but is not limited to, more specific and detailed responses to questions and submitting tangible evidence (including third-party test reports, raw performance data logs, and detailed subsystem schematics) to support the vendor-provided descriptions.

5.4 Step 3 – Cleared Status and Basic Ordering Agreement

Upon invitation, offerors shall submit a Full Proposal to establish a BOA. The proposal shall consist of the following volumes:

• Technical Volume: If requested, a single, consolidated, and finalized technical package based on all documents submitted during Step 1 (Initial Assessment Packet) and Step 2 (Verification Activities Questionnaire).

*If no technical specifications or documents have changed since the Step 2 submission, offerors may simply submit a formal letter certifying that the previously submitted packet is complete, accurate, and serves as their final Technical Volume. Notwithstanding this option, the Government always reserves the right to request a fully consolidated package or additional updated information at its sole discretion to establish the final BOA.

• Price/Business Volume: A comprehensive pricing proposal intended to become the official price list for the BOA. This must include pricing for, at a minimum:
  • The complete, operational UAS (the core UAS system), if applicable.
  • All available mission payloads.
  • A list of recommended spare parts.
  • Standard repair services (e.g., hourly rates, common repair costs).
  • Operator and Maintainer training services.
  • Technical support services (e.g., field service representative support).
  • Standard Commercial Warranty information.

Offerors shall identify any technical data or computer software to be furnished with restrictions by completing the assertion table prescribed in DFARS 252.227-7017. This table must be submitted as an attachment to your proposal.

6. Evaluation Criteria

6.1 Step 1 – Initial Capability Assessment

6.1.1 Initial Acceptance Packet (IAP) Evaluation

Evaluation Focus:

The Government will evaluate the offeror’s IAP to assess the proposed solution’s alignment with the Government’s needs, technical feasibility, and innovation, based on its described Operational Effectiveness, System Integrity, Logistics, and Technical Merit.

Evaluation Ratings:

Fully Compliant:

The IAP and proposed solution appear to meet all key performance parameters and requirements.

Partially Compliant:

The IAP and proposed solution do not meet all key requirements but has significant technical merit or an innovative approach that warrants further consideration.

Unacceptable:

The IAP and proposed solution are not technically sound, does not meet program priorities, or is otherwise inappropriate for further consideration.

Outcome:

Offerors whose submissions are rated Fully Compliant or Partially Compliant may be invited to participate in the Flight Demonstration.

Opportunity for Revision and Resubmission:

Should an IAP be rated Unacceptable or otherwise deemed incomplete, the Government may, at its discretion, provide feedback to the offeror. Offerors are permitted to revise their IAP and resubmit it for re-evaluation at a later date in accordance with the continuous, rolling basis of this CSO.

6.1.2 Demonstration Evaluation

Evaluation Focus:

The demonstration will be evaluated on a pass/fail basis against the key performance parameters and mission scenarios defined by the Government. The purpose is to verify the technical capabilities claimed in the IAP. This will be a contractor-owned, contractor-operated event. To facilitate this, the Government will provide a Demonstration Coordination Packet to offerors once their submission achieves ‘Ready for Demo’ status during IAP processing. This packet will provide comprehensive guidance for the event and will include the following components:

• Test Range and Airspace Information: Details on the designated test range location, logistical and site access instructions, and the process for coordinating airspace. This will also include range-specific safety protocols and any operational constraints.
• Flight Cards: A detailed plan, developed by the Government, outlining the specific maneuvers, payload demonstrations, C2 link checks, and safety procedures required to verify the system’s capabilities during the live flight event.
• Spectrum Management and Requirements: A detailed description of the process for managing spectrum and the information required from the vendor to secure frequency approval. This includes providing the system’s emission characteristics, which are needed for deconfliction and compliance with DoW spectrum policy.
• Vendor Attendance: To ensure a safe and efficient demonstration, attendance will be limited to essential personnel. The Government will coordinate with the offeror to finalize the number of attendees prior to the event.
• Flight Demonstration Readiness Review: One week prior to the scheduled demonstration, the Government will conduct a readiness review using a standardized template. This mandatory review will serve as a final check to ensure all logistical, technical, and safety requirements have been met before the vendor and government teams deploy for the event.  Upon successful review, the offeror will be notified that the demonstration is ready to proceed.
• Flexible Evaluation for Non-UAS Technologies: The demonstration evaluation process is designed for flexibility, extending beyond live flight demonstrations for UAS. To accommodate non-UAS solutions, demonstrations can be conducted through various methods tailored to the system. These may include hands-on bench-top demonstrations, virtual walkthroughs using collaborative software like Microsoft Teams, or other appropriate formats to effectively verify technical capabilities. This adaptable approach ensures all technologies are assessed thoroughly against Government requirements.

Evaluation Ratings:

Successful:

The system successfully demonstrated the required technical capabilities and performance.

Unsuccessful:

The system failed to demonstrate the required technical capabilities and performance.

Outcome:

Only offerors who receive a Successful rating will be eligible for onboarding. Based on their pre-existing NDAA compliance status, they will be invited to submit a Full Proposal (Step 3) and will be onboarded with either a ‘Provisional’ or ‘Cleared’ status.

6.2 Step 2 – Provisional Onboarding and NDAA Compliance Assessment

6.2.1 NDAA Compliance Evaluation

This evaluation is conducted for offerors who have not provided sufficient pre-existing proof of compliance with applicable National Defense Authorization Act (NDAA) supply chain mandates, including NDAA FY2020 Sec. 848, NDAA FY2023 Sec. 817, and NDAA FY2024 Sec. 1821. Such offerors are placed in a Provisional status on the Marketplace pending the outcome of this evaluation.

Evaluation Focus:

The Government will conduct a comprehensive, multi-stage security audit designed to ensure supply chain integrity and operational security. This audit includes:

• A List of Components evaluation, system teardown, and supply chain investigation to trace the origin of every critical hardware and software component.
• Cybersecurity and software vetting, including penetration testing and code review to identify vulnerabilities, malicious code, and unauthorized data exfiltration paths.
• A critical component analysis to confirm that key systems such as flight controllers, data links, and ground control software are free from parts sourced from covered foreign entities.
• A system teardown and assessed NDAA Compliance is required for a system to be placed in the Cleared Phase if originally placed in the Provisional Phase. PM UAS will use US Army Organic Assessors to perform the teardown, with labor costs provided by PM UAS. Shipping costs of the system (both ways) are required to be paid by the Vendor.

Evaluation Ratings:

Compliant:

The system is verified to be free from prohibited components and meets all security requirements outlined in the relevant NDAA sections.

Non-Compliant:

The system was found to contain components or software from a covered foreign entity or otherwise failed to meet the Government’s security requirements.

Outcome:

Only offerors who receive a Compliant rating will have their status updated to Cleared and be invited to proceed to Step 3.

6.2.2 Verification Activities Evaluations

*Note to Offerors:

Verification Activities (VA) are an ongoing effort to generate relevant data for the Marketplace storefront. These activities are conducted for products in both Provisional and Cleared status (i.e., during both Step 2 and Step 3) to populate the detailed product profile on the storefront.

Based on the offeror’s submitted Verification Activities Questionnaire (VAQ), including any attachments, and subsequent Government assessments, the system will be evaluated against the following activities:

• Operational Usage Data
• Detailed Section 848 of the FY2020 NDAA Compliance / System Tear-down
• Soldier Evaluations
• Interoperability / MOSA Critical Utilities
• Comprehensive Cyber Penetration Testing
• Follow-on Manufacturing Maturity / Capacity Assessment
• Additional Government-led Capability Verification (E3, Spectrum, Dynamic, Environmental, and Flight Test)
• Army Network Integration

Verification Reporting:

For each verification activity, the Government will document the system’s demonstrated capabilities and performance. This report will note the observed results and describe any significant factors that may have influenced the system’s performance and the resulting data. The report is then formally recorded and displayed on the Marketplace storefront for authorized Government users to provide a transparent, detailed view of the system’s performance.

Evaluation Rating:

Compliant:

The offeror has submitted the VAQ.

Non-Compliant:

The offeror has failed to submit the VAQ.

Outcome:

The results of all completed Verification Activities are formally documented and published to the system’s profile on the UAS Marketplace storefront to inform Government buyer decisions.

6.3 Step 3 – Cleared

Evaluation Focus:

The Government will evaluate the offeror’s submitted pricing to ensure it is fair and reasonable. Fair and reasonableness will be determined by comparing pricing against the offeror’s standard commercial pricing.

Evaluation Rating:

If the proposed price is not deemed fair and reasonable, the Government may enter into exchanges with the offeror.

Outcome:

Upon determination of technical acceptability and fair and reasonable pricing, a BOA will be established. The Government reserves the right to use other available commercially available contracts in addition to orders placed against a BOA.

Basis for Onboarding:

The Government intends to onboard the offeror to the UAS Marketplace and establish a BOA with any responsible offeror who (1) is rated Fully Compliant or Partially Compliant on the IAP, (2) receives a Successful rating for the flight demonstration, (3) achieves a Compliant rating during the NDAA evaluation, and (4) submits a price proposal that is determined to be Fair and Reasonable.

6.4 Post-Onboarding: End-User Selection & Competition

Following successful onboarding, vendors will compete for individual orders on the UAS Marketplace. Acceptance onto the Marketplace and receipt of a BOA does not establish a minimum order guarantee; the selection of systems and procurement quantities will be determined solely by end-users. This competitive environment is designed to reward vendors whose offerings provide the most overall value to the Soldier.

End-users (i.e., Soldiers) will conduct a competitive selection among all systems available on the Marketplace to fulfill their specific mission requirements. The basis for selection will be a most advantageous determination for the specific mission, considering the following factors:

System Capabilities:

The end-user will evaluate the degree to which the offered system’s operational characteristics meet the specific needs of the unit.

Price:

The total price offered for the system.

Lead Time:

The time required for delivery after order placement.

The end-user will conduct a trade-off analysis among these factors to determine the most advantageous solution. This process ensures that vendors are directly incentivized to innovate and improve upon all aspects of their solution, such as Right-to-Repair and Interoperability, as superior overall value increases their competitiveness for future orders.

7. General Information and Questions

Questions are to be sent only to the Procurement Contracting Officer and Contract Specialist. The following shall be utilized in the email subject line: Call for Solution – [Insert Call Number] (reference the section area). Material questions and answers will be published on www.sam.gov.

8. Contact Information

Role

Name

Email

Procurement Contracting Officer

Latoya S. Pryor

usarmy.redstone.acc.mbx.acc-rsa-uas-marketplace@army.mil    

Contract Specialist

Maryssa Sanchez

10. Organizational Conflict of Interest (OCI)

The Offeror shall perform an OCI analysis and submit the results of that analysis in addition to the IAP submission. Specifically, the Offeror shall analyze the details of the Call and the implementation of their proposed Solution for actual or potential OCI situations associated with the performance of the Offeror, or any of the Offeror’s proposed teammates or subcontractors, under any contract or agreement the Offeror or the Offeror’s teammates or subcontractors have been or may be awarded by any federal agency or other entity. The Offeror shall describe in detail the methodology used to identify actual or potential OCI issues. The level of detail for OCI analysis may not be the same for all vendors. FAR 9.5 may be used as guidance for OCI analysis. If no conflicts are identified, a risk mitigation plan is not required; however, a description of the analysis methodology, and an affirming statement that no conflicts are identified shall be included.

If the Offeror identifies any actual or potential OCIs with respect to the performance of the Offeror or the Offeror’s subcontractors or teammates, the contractor shall provide an OCI Mitigation Plan to be incorporated as an attachment to any resulting contract or agreement. Any proposed avoidance or mitigation techniques shall be consistent with FAR 9.5 and the most recent decisions of the Government Accountability Office (GAO) and the U.S. Court of Federal Claims.

11. Non-Government Advisors

Offerors are advised that non-Government personnel may be used to assist in the evaluations for this Call. Non-Government advisors will be bound by appropriate non-disclosure agreements (NDAs) with the Government to protect proprietary and competition-sensitive information. By submitting a response to this CSO, the offeror acknowledges this process and waives any and all claims against the Government for any disclosures of proprietary information by non-Government personnel. If an offeror executes a direct NDA with the non-Government advisors, a copy of the signed agreement must be included with their submission.

12. Attachments

Attachment 1. Statement of Objectives (SOO)