C4S _SOO_C2 SDK Integration Event_13AUG26.docx

Attachment 001

Statement of Objectives (SOO) USG C2 SDK Integration Event 06 August 2026

1.

INTRODUCTION AND PURPOSE

This Statement of Objectives (SOO) defines the high-level objectives for innovative, commercially available Group 1-3 Uncrewed Aircraft Systems (UAS), Launched Effects (LE), Unmanned Ground Vehicles (UGV), control subsystems and supporting software solutions to be onboarded into the industry-informed, USG Command and Control (C2) architecture.

The purpose of this document is to outline the Government's overall objectives for the hardware, software, and lifecycle support services required to support the Government’s quarterly USG C2 SDK Integration events. It is not a prescriptive SOO. To be eligible for consideration under this Commercial Solutions Opening (CSO) Call for Solutions (C4S), offerors must propose solutions that are demonstrably innovative and commercially available and participate in the USG C2 SDK Integration Event. The Government's objective is to then acquire these solutions through the offeror's established commercial practices for delivery, training, and support.

2. BACKGROUND

Soldiers need an integrated C2 solution to conduct operations and maneuver as a team with RAS integrated into NGC2. The current portfolio of disparate, stove-piped control systems makes this level of integrated command and control impossible, creating operational seams the enemy can exploit. The USG’s C2 architecture solution provides scalable control capabilities to enable the simultaneous operation of heterogenous RAS in the formation. Control services are provided to enable one or more operators to execute control simultaneously on the network as a team. This consolidates and integrates these control capabilities as services in NGC2 for networked operations. PM UAS seeks to minimize barriers to integration for RAS systems to the USG C2 architecture. The USG C2 SDK Integration event will provide vendors of controllers/Human Machine Interfaces (HMI) for Group 1-3 UAS, Launched Effects (LE), and Unmanned Ground Vehicles (UGV) the opportunity to rapidly integrate with the USG’s C2 architecture solution, test their solution against the Army network, and receive immediate soldier-driven feedback on their systems. This SOO supports that goal by defining the objectives for innovative commercially available solutions that can be integrated with the USG’s C2 architecture.

3. SCOPE

This SOO applies to all innovative Group 1-3 UAS, LE, UGV, controllers/HMIs, and supporting software solutions sought under the companion C4S. Solutions must be capable of performing or enabling missions such as Reconnaissance, Surveillance, and Target Acquisition (RSTA), electronic warfare, communications relay, or strike to enhance the capabilities of Army units at echelons above battalion.

3.1. For RAS systems (e.g., Group 1-3 UAS, LE, and UGVs), the primary objective is to demonstrate alignment to or integration with the USG C2 architecture to publish information to the tactical network. Key objectives include:

· Extended Reach: Ability to operate at the ranges required by echelons above battalion.

· Autonomous/Semi-Autonomous Operation: Capability to execute missions in contested environments with minimal operator interaction.

· Mission Diversity: Effectively perform missions including, but not limited to, strike, electronic warfare, and reconnaissance.

· Collaborative Teaming: Ability to network and operate as part of a collaborative swarm or team of unmanned systems.

3.2. For controllers/HMIs, the primary objective is to demonstrate alignment to or integration with the USG C2 architecture via the User Control Gateway to publish information to the tactical network. Key objectives include:

· Controller Interoperability: Ability to reduce logistical burden to the Warfighter by controlling different RAS platforms with the same controller.

· Heterogeneous Control: Ability to control different RAS platforms simultaneously with a single controller.

3.3. For supporting software solutions, the primary objective is to demonstrate the augmentation of C2 capabilities, the integration of intelligent contextual reasoning at the tactical edge, the implementation of policy-driven governance, and the extension of interoperable communication across tactical networks. Key objectives include:

· Policy-Driven System Governance: Ability to ingest operational policies, commander's intent, or Rules of Engagement (ROE) via natural language documents, Domain-Specific Languages (DSLs), or other machine-interpretable formats. The software must dynamically apply these ingested rules to autonomously govern, constrain, and guide system behavior during mission execution.

· Contextual Reasoning & Edge Intelligence: Ability to ingest, process, and reason through localized data in real time as mission variables shift. This includes incorporating machine learning algorithms, computer vision, or signal processing capabilities to enable the software to dynamically adapt mission execution and drastically reduce the cognitive burden on the operator.

· C2 Augmentation: Ability to enhance the provided core software framework to support advanced orchestration, automated decision support, and streamlined management of autonomous systems in the battlespace.

· Tactical Protocol Integration: Capability to extend software communications to effectively exchange data over tactical edge networks utilizing diverse military and commercial protocols, to include Cursor on Target (CoT), LINK16, and Lattice by Anduril.

· Data Interoperability: Ability to ensure seamless integration, translation, and information sharing between disparate RAS platforms and higher-echelon command nodes to maintain a common operating picture.

3.4. 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.

4. OBJECTIVES

The overarching objective is for the contractor to provide an innovative and complete commercial UAS, LE, UGV, Controller/HMI, or supporting software solution. The contractor shall propose their standard commercial offerings that best meet the following objectives and their ability to integrate their system with the USG’s integrated C2 architecture solution.

4.1. System Attributes

Vendors must provide information addressing each attribute as part of their white paper response to include their product’s Technology Readiness Level (TRL). This information provides the basis for the Government to make selections of the UAS, LE, UGV, Controller/HMI, or supporting software solutions for each integration event that best meets their needs.

· Modular Open Systems Approach (MOSA): Vendors shall articulate their MOSA strategy. This will include detailing how interoperability is achieved for major subcomponents, with a particular focus on payloads and radios. The vendor will specify what data will be provided to the Government above and beyond typical commercial procurement to support integration and future upgrades.

· Future Airborne Capability Environment (FACE): Vendors shall articulate their FACE strategy. This will include detailing how their software aligns to the FACE Technical Standard, explicitly stating whether they are utilizing an established FACE software framework or a custom implementation. If leveraging an existing framework, the vendor shall indicate which framework is used and specify the aspects or components being employed across the different FACE segments. If providing a custom implementation, the vendor must describe how software portability, reusability, and interoperability are achieved, detailing how their Units of Conformance (UoCs) align with the five segments of the FACE Reference Architecture. Regardless of the approach, the vendor will specify what architectural artifacts, software components, and interface definitions will be provided to the Government.

· Government Right to Repair and Right to Modify: The Government’s objective is to secure the rights necessary to support an organic, field-level maintenance, repair, and modification capability. It is anticipated that this procurement will be conducted in accordance with FAR Part 12, establishing standard commercial data rights as the baseline. The Government, however, seeks to negotiate for enhanced rights beyond this standard. To that end, the vendor must provide a comprehensive plan that addresses the specific data rights objectives detailed in Section 8.0. This plan must identify the data and Intellectual Property (IP) rights the Government will be granted to repair and modify the system, note any limitations, and propose a strategy to address them. The specific terms for these enhanced rights are negotiable.

· USG C2 Core Capabilities: The white paper response will be used to gather information on the offering’s ability to address any of the USG’s integrated C2 architecture core control capability requirements:

· Asymmetric Control: Dynamic control roles and modes among numerous operators and systems.

· Distributed Control: Dynamic control configuration based on connectivity and availability of assets.

· Intelligent Control: AI capability as control services (internal to the C2 architecture) or surfaces (external to the C2 architecture).

· Intermodal Control: Dynamic control translation between control modalities.

· Policy-Based Control: Dynamic control authorization based on conditions or configurations.

· Resilient Control: Dynamic control allocation based on operational conditions or configuration.

4.2. Required Supporting Deliverables and Services

To meet the objectives outlined above, the offeror shall provide or be capable of providing the following items. Specific quantities, configurations, and delivery schedules will be defined in each individual order.

· Data & Documentation:

· Technical Manuals: Standard commercial Operator and Maintainer manuals sufficient for Government personnel to perform field-level maintenance.

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

5. 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.

5.1. Data Rights for External Interfaces

To support the Government's Modular Open Systems Approach (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., USG C2 architecture, platforms, controllers). This is critical to ensure future interoperability and enable competitive hardware and software upgrades.

5.2. Data Rights for Maintenance, Repair, Modification, and Training To enable Government-led training and organic, field-level sustainment, the Government's objective is to obtain the necessary commercial license rights to use, reproduce, and distribute all technical documentation (e.g., operator manuals, maintenance manuals, training materials) within the Government.

6. PLACE OF PERFORMANCE

The delivery and performance of the USG C2 SDK Integration Event will occur at a location to be determined for each event.

7. SECURITY OBJECTIVES

The contractor shall adhere to the following security objectives in supporting the USG C2 SDK Integration Event.

7.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.

7.2. Classification

The base effort under this SOO is UNCLASSIFIED. No classified access is required to integrate into the USG C2 architecture nor participation in the integration events. If integration requires such access, 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.

7.3. Software Supply Chain Risk Management (SCRM)

The contractor shall have and maintain a process for managing software supply chain risk for key components (e.g., flight controllers, communications hardware, GPS modules, processing units) and software tools. 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.

7.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.

8. INSPECTION AND ACCEPTANCE

The Government's inspection and acceptance of all items and services will be conducted in accordance with the terms specified in each individual order. Unless otherwise stipulated in an order, inspection may be based on the contractor's standard commercial quality control system or certificates of conformance. Final acceptance will be performed by an authorized Government representative at the delivery destination specified in the order.

image1.png