Call CSO002 JATF AOIs.pdf

SOF AT&L Innovative Technology and Agile Acquisition

Commercial Solutions Opening (CSO) CALL CSO002

Joint Acquisition Task Force (JATF)

17 March 2026

EXECUTIVE SUMMARY: This CSO call is intended to meet the requirements of DFARS 212-70 Commercial Solutions Opening. The intent of this notice is to establish a USSOCOM SOF AT&L JATF CSO call with a tailored scope to meet the specific requirements of this call.

Interested Vendors may submit a solution brief in response to Call CSO002 from the dates 18 March 2026-01 April 2026, only.

NOTE: All submissions must include “CALL CSO002” in the email subject line and should address ONLY AOIs I and/or II below.

THE OPERATING ENVIRONMENT:

The operational environment for special operations unmanned systems (UxS) is defined by complexity and constant adaptation. Deployed globally in con-tested areas, Special Operations Forces (SOF) rely on these systems for mis-sions ranging from counterterrorism to strategic competition. Success in this dynamic battlespace hinges on close collaboration with forward-deployed partners to counter shared, rapidly evolving threats. This reality dictates the need for UxS technologies that is small, rugged, modular, and optimized for low-power, multi-use applications in the planet's most extreme environments.

OPEN ARCHITECTURE AND INTEROPABILITY: All proposed solutions, regardless of the capability area, must be built upon a foundation of modularity, interoperability, and open standards. Proposals for closed, proprietary systems that inhibit third-party integration or prevent data portability may be considered non-compliant and at a significant competitive disadvantage. Our strategic intent is to foster a "system of systems" environment, not to procure a collection of siloed capabilities. Offerors must explicitly describe their approach to open architecture, their use of widely accepted standards (e.g., C5ISR/EW Modular Open Suite of Standards (CMOSS), Sensor Open Systems

Architecture (SOSA), and how their system enables data, analytics, and components to be portable, scalable, and upgradeable by different vendors.

The long-term cost of integration and the freedom from vendor lock-in are elements that will be assessed as part of the evaluation criteria.

AREAS OF INTEREST (AOIs)

AOI I: Unmanned Systems (UxS) Family of Systems (FoS) – Maritime:

Seeks the development and integration of a multi-mission maritime UxS Family of Systems (FoS) that function as a unified and interoperable capability. A primary objective is the implementation of a common control interface that allows a single operator to command, control, and monitor multiple UxS across all domains. Solutions should minimize operator cognitive burden while preserving flexibility, responsiveness, and precision control. Emphasis is placed on interoperability, modular payloads, open architectures, and common control standards that enable rapid mission reconfiguration and seamless cross-platform integration.

In this AOI, innovation is about the integration and interoperability that create a true FoS. The team will consider innovative solution such as but not limited to:

(a) Demonstrates a True "Common Controller" that allows a single operator to intuitively manage multiple, heterogeneous UxS (e.g., a maritime USV and an aerial UAS) from a single interface, significantly reducing cognitive load.

(b) Applies a Novel Commercial Technology, such as a user interface from the gaming industry or a fleet management system from the commercial logistics sector to the military problem of multi-domain unmanned operations.

(c) Creates a "Universal Translator" for UxS payloads, allowing a sensor or communication package to be rapidly swapped between an air, ground, and maritime platform with minimal reconfiguration.

(d) Enables Autonomous Collaboration, where multiple unmanned systems from different domains can share data and coordinate actions to achieve a single mission objective without direct, continuous operator input.

AOI II: Theater Edge Innovation Labs (TEIL):

Includes capabilities that enhance UxS training, modification, integration, and sustainment in CONUS and OCONUS locations with partners through TEIL-enabled infrastructure, fabrication equipment, materials, and tools. Areas of interest encompass dedicated UxS training, integration, and testing facilities;

engineering, design, prototyping, and integration equipment; additive manufacturing and 3D printing enablers; and other tools that support hands-on training, rapid modification, repair, and lifecycle sustainment of UxS platforms. Solutions that reduce time to proficiency and empower personnel to adapt and evolve UxS capabilities, and forward unmanned systems factories collocated with international partners at the tactical level are of particular interest.

In this AOI, innovation focuses on the ecosystem of support, training, and sustainment that empowers the warfighter to adapt and maintain UxS capabilities at the tactical edge. The team will consider innovative solution such as but not limited to:

(a) Leverages Augmented Reality (AR) or Virtual Reality (VR) to create immersive, hands-on training modules that can drastically reduce the time it takes for an operator to become proficient in flying, maintaining, or repairing a new UxS platform.

(b) Develops a "Factory-in-a-Box" Concept that packages additive manufacturing (3D printing), design software, and materials into a rapidly deployable kit, enabling forward-deployed units to print custom parts and modifications on demand.

(c) AI-Driven Predictive Maintenance Applies, using a software platform that analyzes UxS usage data to predict component failures before they happen, increasing fleet readiness and simplifying logistics.

(d) Creates a Digital Integration Workbench, a software and hardware environment that allows engineers and operators to rapidly test and validate new payloads, software updates, or third-party components on a UxS before live deployment.

(e) Commercial capabilities that provide support to SOF personnel and partners to rapidly integrate and/or modify existing UxS with off-the-shelf technologies.

1. INTRODUCTION:

1.1 The United States Special Operations Command (USSOCOM) has established a Joint Acquisition Task Force (JATF) within the Special Operations Forces Acquisition, Technology, and Logistics (SOF AT&L) Center to accelerate the development, procurement, and integration of commercially derived technologies to address current interest areas and future flexible and defensive capabilities.

1.2 The USSOCOM SOF AT&L Center JATF seeks to award FAR and

non‐FAR Contracts and Agreements to nontraditional and traditional defense contractors to carry out prototype projects that are directly relevant to enhancing the mission effectiveness of the SOF Operator and the supporting platforms, systems, components, or material to be acquired or developed by the USSOCOM, or the improvement of platforms, systems, components, or materials in use by USSOCOM.

1.3 This Commercial Solutions Opening (CSO) call may make awards to proposals for innovative, commercial technologies through a multi‐phased, competitive process.

1.3.1 Phase I: Initially, solutions will be sought on a full‐and‐open basis under certain technological areas, or industry sectors, characterized by Areas of Interest (AOI). Initial submissions against these AOIs will be requested as Solution Briefs (SB) mainly in the form of a White Paper (WP). A team of Government personnel who are subject matter experts for the given AOI will evaluate each submission independently against standard criteria for advancement to Phase II. The Government may elect to proceed directly to Phase III after a successful Phase I evaluation.

1.3.2 Phase II: If a Phase II evaluation is necessary, the Government will host Phase II invites at one of its facilities wherein each company will have an allotted amount of time to pitch or demonstrate its proposed solution to the Government evaluation panel and hold any discussions necessary for evaluation. Discussions may continue outside of the pitch or demonstration session. Participation in Phase II will be entirely at the company’s expense.

Favorably evaluated pitches will receive a Request for Prototype Proposal (RPP) that marks the beginning of Phase III. Note, Phase II is optional for this CSO process, and may not always be conducted, or may not be required for every successful Phase I submission.

1.3.3 Phase III: The Government will only advance companies to Phase III only if it intends to solicit a detailed cost or price proposal from that company. Companies selected for Phase III will be evaluated strictly in accordance with the evaluation factors and processes outlined in the resulting

RPP.

2. GUIDELINES FOR SOLUTION BRIEFS, PITCHES, AND PROPOSALS:

2.1 The purpose of the Solution Brief is to identify innovative solutions and preclude effort on the part of the Company whose proposed work may not be of interest to the Government. Companies are encouraged to follow the instructions detailed below. Solution briefs should specifically identify the AOI on the CSO website to which it is responding. The Government aims to provide an evaluation response 15 days after the submission deadline for Solution Briefs in response to an AOI.

2.2 Submissions will not be returned. The original of each submission received will be retained by the USSOCOM SOF AT&L JATF and all other non‐ required copies destroyed.

2.3 Guidelines for Solution Brief Submissions:

2.3.1 It is generally desired that active Research and Development (R&D) is underway for concepts submitted under this CSO. Active R&D includes analytical studies and laboratory studies to physically validate the analytical predictions of separate elements of technology, as well as software engineering and development.

2.3.2 Costs of preparing and submitting solution briefs are at the company’s expense.

2.3.3 Unnecessarily elaborate brochures or proposals are not

desired.

2.3.4 Use of a diagram(s) or figure(s) to depict the proposed solution is strongly encouraged.

2.3.5 Multiple solution briefs addressing different topic areas may be submitted by the same organization; however, each solution brief may only address one concept based on the stated Government AOI.

2.3.6 The period of performance for any solution brief or proposal submitted under this CSO should generally be no greater than 18 months.

2.3.7 Technical data with military application may require

appropriate approval, authorization, or license for lawful exportation.

2.3.8 All solution briefs shall be unclassified. Solution briefs containing data that are not to be disclosed to the public for any purpose or used by the Government except for evaluation purposes shall include the following sentences on the cover page:

“This solution brief includes data that shall not be disclosed outside the Government, except to contractor support services personnel for evaluation purposes, and shall not be duplicated, used, or disclosed ‐‐ in whole or in part ‐‐ for any purpose other than to evaluate this submission. If, however, an agreement is awarded to this Company as a result of ‐‐ or in connection with ‐‐ the submission of this data, the Government shall have the right to duplicate, use, or disclose the data to the extent agreed upon by both parties in the resulting agreement. This restriction does not limit the Government's right to use information contained in this data if it is obtained from another source without restriction. The data subject to this restriction are contained in sheets [insert numbers or other identification of sheets]”

And each restricted data sheet should be marked as follows:

“Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposal.”

2.3.9 Foreign‐Owned businesses may be a submitter alone or

through some form of teaming arrangement with one or more United States‐ owned businesses. However, the ability to obtain an agreement based upon a submission may depend upon the ability of the Foreign Owned business to obtain necessary export clearances and approvals to obtain AOI or SOI information.

2.3.10 Questions regarding the objectives or preparation of the solution brief should be addressed to: JATF2@socom.mil

2.3.11 Submissions must be submitted electronically via email to the following individuals:

Mr. Ron Reed – Ronald.e.reed.civ@socom.mil Mr. James Helmick – James.s.helmick.civ@socom.mil Mrs. Juanita Bell – Juanita.bell.ctr@socom.mil LTC Trevor Money – trevor.money@socom.mil

2.4 Solution Brief Preparation and Evaluation: Submitter’s solution brief should not exceed five (5) pages using twelve (12) point font. Alternatively, solution briefs may take the form of slides, which should not exceed ten (10) slides. These limits are not requirements, but strong recommendations.

2.4.1 Solution Brief Content:

· Title Page (does not count against page limit) Company Name, Title, Date, Point of Contact Name, Email Address, Phone, and Address

· Executive Summary (one page) Provide an executive summary of the technology.

· Technology Concept: Describe the unique aspects of your technology and the proposed work as it relates to the AOI. Identify whether the effort includes the pilot or demonstration of existing commercial technology (identified as commercially ready and viable technology), or the development of technology for potential commercial or defense applications. If development or adaptation is proposed, identify a suggested path to mature technology.

· Company Viability: Provide a brief overview of the company. Provide a summary of current fundraising to date or a summary of the top line (gross sales or revenues). Provide a summary of product commercialization and go‐ to‐market strategy.

2.4.2 Solution Brief Basis of Evaluation: Individual solution briefs will be evaluated without regard to other submissions received under this announcement against the following criteria:

· Technical Merit – the feasibility of the proposed solution to address the AOI.

· Relevancy – how the proposed solution relates to the AOI.

· Innovation – degree to which the proposed solution provides an innovative, unique and/or previously under-utilized approach.

· Business Viability – strength of the company and commercial viability of the proposed solution. Business viability includes ability to withstand a due diligence analysis, including from a foreign owned and controlled perspective.

It may require Trade Agreements Act (TAA) compliance. The Government may elect to use external market research in the evaluation of a company’s viability.

· Affordability – cost price and other budgetary considerations.

2.4.3 After evaluating the Solution Brief the Government may elect to invite a Company to pitch and/or demonstrate their technology in person or request additional information from the Company.

2.5 Pitch and/or Demonstration Content: The pitch and/or

demonstration should provide more details on the technical merit and business viability of the proposed solution submitted in the Solution Brief.

Regardless of format, the pitch and/or demonstration must also address:

· Rough Order of Magnitude price and notional schedule

· USSOCOM Utility and how this concept could be tested within a SOF military environment.

· Operational Impact. Details who the operational users of the technology are expected to be.

· Prototype: State how this effort fits the CSO definition of a prototype.

· Data Rights and Intellectual Property Assertions.

· The Government may request additional information outside of the pitch/demonstration.

2.6 Pitch and/or Demonstration Basis of Evaluation: Individual pitch and/or demonstration will be evaluated without regard to other presentations under this announcement. Evaluation will be IAW the pre-stated evaluation factors in paragraph 2.4.2.

2.7 The Government will aim to complete Phase II evaluations and Company notification within 15 calendar days of the pitch/demonstration and/or receipt of additional requested information. All companies will receive Phase II notification, however, only favorably evaluated pitches/demonstrations will enter Phase III of the CSO process and receive a Request for Prototype Proposal (RPP).

2.8 Proposal Preparation: RPPs will include preparation instructions for Prototype Proposals. During this Phase, companies will collaboratively develop Statements of Work (SOW) with the Government teams for their specific projects and negotiate Terms and Conditions into their Contracts or Agreements.

3. CONTRACT AWARD:

3.1 Only Warranted Contracting Officers and Agreements Officers may obligate the Government and issues awards for Procurement Contracts or Other Transaction Agreements (OTA).

3.2 Awards made under this CSO will be either FAR‐based Firm Fixed‐ Price contracts or Other Transaction Agreements (OTA) under 10 U.S.C. § 4022 for Prototypes Projects with potential follow‐on noncompetitive Production Agreements, or 10 U.S.C § 4023 Procurement for Experimental Purposes Contract type will be determined during Phase III.

3.3 In the event an OTA is awarded under 10 U.S.C. § 4022 for a Prototype Project, a follow‐on production agreement may be awarded to the Prototype Project recipient in a non‐competitive manner based on completion of success criteria listed in the Prototype Project. Non‐completion of all success criteria does not limit the possibility of the non‐competitive follow‐on production OTA, and the noncompetitive production OTA may also be awarded before the overall completion of the Prototype Project.

3.4 To receive an award, Companies must be a registered entity in the System for Award Management (SAM). This system verifies identity and ensures that payment is sent to the right party. The link can be found here: https://sam.gov/SAM/

3.5 In general, to invoice and receive payment, Companies must register in Wide Area Work Flow (WAWF). The Contracting Officer/Agreements Officer will provide WAWF assistance during Phase III.

3.6 Proposals will be accepted through the date of 1 April, 2026.

4. NON‐GOVERNMENT ADVISORS: Non‐Government advisors may be used in the evaluation of solution briefs and proposals and will have signed non‐ disclosure agreements (NDAs) with the Government. The Government understands that information provided in response to this CSO is presented in confidence and may contain trade secret or commercial or financial information, and it agrees to protect such information from unauthorized disclosure to the maximum extent permitted and as required by Law.

5. CONTACT INFORMATION: Be advised, only a Contracting Officer/Agreements Officer has the authority to enter into a binding agreement on behalf of the Government and has exclusive authority to change the terms of a contract or agreement. All inquiries need to be sent to JATF2@socom.mil

6. DEFINITIONS:

Innovative: “Innovative” is defined as (1) Any technology, process, or method, including research and development, that is new as of the date of submission of a proposal; or (2) Any application that is new as of the date of submission of a proposal of a technology, process, or method existing as of such date.

Non‐traditional Defense contractor (NDC**):** An entity that is not currently performing and has not performed, for at least the one‐year period preceding the solicitation of sources by DoD for the procurement or transaction, any contract or subcontract for the DoD that is subject to full coverage under the cost accounting standards prescribed pursuant to section 1502 of title 41 and the regulations implementing such section (see 10 U.S.C. 2302(9)).

Other Transaction Agreement (OTA): Legally binding instruments not subject to the requirements of the Federal Acquisition Regulation (FAR) obligating the Government for a purpose 10 U.S.C. § 4022.

Procurement contract. A contract awarded pursuant to the Federal Acquisition Regulation.

Prototype Project: Prototype project addresses proof of concept, model, reverse engineering to address obsolescence, pilot, novel application of commercial technologies for defense purposes, agile development activity, design, development, demonstration of technical or operational utility, or combinations of the foregoing. A process, including a business process, may be the subject of a prototype project.

Although assistance terms are generally not appropriate in OT agreements, ancillary work efforts that are necessary for completion of the prototype project, such as test site training or limited logistics support, may be included in prototype projects. A prototype may be physical, virtual, or conceptual in nature. A prototype project may be fully funded by DoD, jointly funded by multiple federal agencies, cost‐shared, funded in whole or part by third parties, or involve a mutual commitment of resources other than an exchange of funds.