Statement of Objectives for MEL-LEDGR-BMS.docx

Attachment 001

Statement of Objectives (SOO) Technical Presentations to Inform Army Aviation’s Launch Approach for Launched Effects (LE) from Ground and Air 20 May 2026

Distribution Statement D: Distribution authorized to the Department of War and U.S. DoW contractors only; Administrative or Operational Use, 21/09/2022. Other requests shall be referred to the CPE Aviation, Unmanned Aircraft Systems Project Management Office (UAS PMO), SFAE-AVN-U, Redstone Arsenal, AL 35898-5000.

1.0 INTRODUCTION AND PURPOSE

This Statement of Objectives (SOO) defines the high-level objectives for innovative, commercial solutions that can complement and/or inform Army Aviation's Launcher Approach. This Call for Solutions does not seek to buy Launched Effects (LE) but rather to inform the USG path forward for its launcher development.

This document is not a prescriptive Statement of Work (SOW). To be eligible for consideration under this Call for Solutions, offerors must propose solutions that are demonstrably innovative and commercially available.

2.0 BACKGROUND

The character and pace of modern warfare are being redefined by the rapid proliferation of UAS. To maintain a technological overmatch, the U.S. Army has established the UAS Marketplace. This strategic initiative marks a pivot from traditional acquisition to a dynamic, free-market concept designed to rapidly identify, assess, and field innovative commercial UAS. This SOO supports that goal by defining the objectives for developing the USG LE launcher approach.

3.0 SCOPE

This SOO applies to all innovative technical approaches sought under the companion Call for Solutions.

3.1 For this USG LE Launcher Approach effort, the primary objective is to inform the USG of technical approaches and interfaces of existing Launched Effects and how those are compatible with current USG-owned launchers. Additionally, the USG is seeking information on other established launch solutions that utilize (Modular Open Systems Approach) MOSA. Key approach aspects include:

· Launched Effects Dispenser for Ground & Rotorcraft (LEDGR) Interoperability

· Information/approaches on products that interface and launch from the USG owned LEDGR

· Industry/Common Launcher approaches

· Information/approaches on products that can provide common carry and launch of multiple LE variants from a MEL

· Modular Effects Launcher (MEL) Interoperability

· Information/approaches of products that can interface and launch from the MEL (ex: LE all up rounds)

· Vendor Software Interoperability

· Information/Approaches on Vendor Software integration into USG Arm and Firm S/W (MOSA Strategy, API Drivers, etc.)

4.0 QUALITY ASSURANCE

The Government's objective is to rely on the contractor's existing quality assurance system. The contractor shall be responsible for delivering products and services that meet its own established commercial quality standards. The Government reserves the right to review the contractor's quality system and processes to gain confidence in the proposed solution.

5.0 UAS MARKETPLACE ACCOUNT MANAGEMENT

The contractor shall provide a single point of contact responsible for managing the UAS Marketplace effort and any Basic Ordering Agreement (BOA) orders. The Government is not directing the contractor to provide a stand-alone project manager but rather identify the point of contact. This arrangement should be consistent with the support provided for customary commercial sales. The contractor may be asked to participate in a post-award conference and subsequent periodic program reviews (e.g., quarterly) with Government representatives to discuss schedule, performance, supply chain status, and other relevant topics.

6.0 TECHNOLOGY REFRESHMENT AND END-OF-LIFE MANAGEMENT

The Government’s objective is to maintain a continuous infusion of innovative technology to the UAS Marketplace. The contractor shall have a standard commercial process for introducing technology refreshments, upgrades, and improvements to its product line. Additionally, the contractor shall have a process for notifying the Government of any components or systems nearing their end-of-life, along with a proposed transition plan to successor products.

7.0 OBJECTIVES

The overarching objective is for the vendors to provide technical information/approaches that inform the USG LE launcher approach. This Call does not seek to procure LE but to inform the USG on development of a launcher approach supporting common LE carriers. The contractor shall propose their standard industry offerings that best meet the following objectives.

7.1 Launcher Approach

Vendors must provide information/approaches addressing one, some, or all attributes as part of the Technical White Paper:

· Launched Effects Dispenser for Ground & Rotorcraft (LEDGR): Army Aviation has a requirement to deploy/forward launch LEs at tactical altitudes. The Government owned LEDGR is a tube based, rocket assisted mechanism, that is available for industry partners who need a launch solution for their LE. The intent is to identify mature LE that could be LEDGR compatible and inform future LEDGR design efforts. Interface Control Documents for LEDGR are available from the USG via Email: UASLaunchAndControl@army.mil

· Industry/Common Launcher Approaches: The USG seeks information and approaches that would provide common carry and launch for multiple LE vendors.

· Modular Effects Launcher (MEL): Vendors shall articulate/show their ability/strategy for interfacing to the USG owned MEL. This will include detailing how interoperability is achieved with particular focus on launching and use of vendor provided launch mechanisms (rocket assist, tubes, etc.). Interface Control Documents for MEL are available from the USG via Email:UASLaunchAndControl@army.mil

· Arm & Fire Integration:

The Department of the Navy's Battle Management System (BMS) is the Government-designated Arm & Fire solution for the MEL and LEDGR. In their technical white paper, vendors must address the following:

Modular Open Systems Approach (MOSA): The vendor shall describe how their proposed system is designed in accordance with a MOSA. This description must detail the system’s software architecture, its use of standardized interfaces for command, control, data exchange, and its established methods for integrating third-party software and hardware components.

Arm/Fire Integration Pathway: The vendor shall provide a technical proposal outlining a feasible path for integrating their system's arm and fire functions with a Government-provided fire control application. This proposal should articulate the specific technical steps, data exchange requirements, and architectural considerations necessary to achieve this integration.

7.2 Required Supporting Deliverables and Services

· To meet the objectives outlined above, the offeror shall provide or be capable of providing the following data & documentation items:

· Interface & Integration Data: To support the Government's MOSA strategy, provide Interface Control Documents (ICDs), Form, Fit, and Function (FFF), Operations, Maintenance, Installation, and Training (OMIT) data for key subcomponents (e.g., payloads, radios).

8.0 DATA RIGHTS OBJECTIVES

The following sections detail the Government’s specific objectives for the enhanced data rights required beyond a standard commercial license. The plan submitted by the vendor (as required in Section 8.1) must address how they intend to meet these objectives.

8.1 Data Rights for External Interfaces

To support the Government's MOSA strategy, the Government’s objective is to obtain, at a minimum, Government Purpose Rights (GPR) for all data and software related to key external interfaces (e.g., payloads, radios). This is critical to ensure future interoperability and enable competitive hardware and software upgrades.

9.0 SECURITY OBJECTIVES

The contractor shall adhere to the following security objectives throughout the period of performance.

9.1 Cybersecurity

The contractor shall maintain a robust cybersecurity posture in accordance with the requirements of DFARS 252.204-7019 and NIST SP 800-171, as stipulated in the overarching Call for Solutions. The primary objective is to ensure all Controlled Unclassified Information (CUI) related to this effort is protected from unauthorized access, use, or disclosure.

9.2 Classification

The base effort under this SOO is UNCLASSIFIED. No classified access is required to obtain a BOA. However, individual orders placed against the BOA may require the handling of classified information. If an order requires such access, a DD Form 254, Contract Security Classification Specification, will be issued with that specific order, and the contractor must possess the appropriate facility and personnel clearances as required by that order.

9.3 Supply Chain Risk Management (SCRM)

The contractor shall have and maintain a process for managing supply chain risk for key components (e.g., flight controllers, communications hardware, GPS modules, processing units). The objective of this process is to ensure the integrity of the delivered system and to comply with all applicable National Defense Authorization Act (NDAA) sourcing prohibitions.

9.4 Operations Security (OPSEC)

The contractor shall implement basic operational security measures to safeguard unclassified but sensitive program-related information. The objective is to prevent the aggregation of information that could provide an advantage to an adversary. This includes, but is not limited to, protecting details regarding specific ordering units, delivery quantities and locations, and deployment timelines from public disclosure.

image1.jpeg