ACPE SOO.pdf

THEATER DEPLOYABLE COMMUNICATIONS

Statement of Objectives

Agile Communications Package Enhanced (ACP-E)

25 August 2025

Prepared by:

AFLCMC/HNIB TDC Program Office

15 Eglin St

Hanscom AFB, MA 01731

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense (DoD) and U.S.

DOD Contractors only; administrative/operational use; 25 August 2025. Other requests for this document shall refer to the AFLMC/HNI, Enterprise IT and Cyber Infrastructure Division, Hanscom AFB, MA 01731.

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

1. Background

Theater Deployable Communications (TDC) provides an extension of the Department of Defense Information Network (DoDIN) and provides the warfighter with flexible, lightweight, modular, scalable, and integrated deployable communications to support the execution of command and control, intelligence, surveillance, and combat support missions.

This equipment provides the operational commanders and warfighters with access to the Defense Information Systems Network (DISN) core services including, but not limited to, Defense Switched Network (DSN), Non-secure Internet Protocol Network (NIPRNet), and Classified Networks.

TDC equipment is packaged in kits and modules that are installed in, transported in, and operated from transit cases. Users access DISN services via the TDC network and by means of such end instruments including, but not limited to, workstations, analog phones, and Voice over IP (VoIP) phones.

Technologies are required to rapidly collect, analyze, and share information and make decisions in real time across dynamic transport capabilities in a possibly heavily contested and degraded communications environment.

2. Purpose

This document is a Statement of Objectives (SOO) for the Theater Deployable Communications (TDC) Agile Communications Package Enhanced (ACP-E). The TDC PMO has a strong desire to build upon and continually enhance the existing ACP by performing a “try, decide, buy” approach leveraging a rapid-prototyping effort with commercially available products with the potential of rapidly fielding an enhanced ACP to the growing user community. The PMO will establish a manner to procure the existing technical baseline during the rapid prototyping portion beyond FY26 and eventually form a path to procure an enhanced version of the ACP at scale. TDC is interested in Commercial-off-the-Shelf (COTS) solutions that can provide mesh networking capabilities while updating baseband equipment to the newest versions as required in future iterations.

3. Objectives

The overall objective is to identify and evaluate solutions to support the technical objectives and demonstrate the ability to be operated by Air Force personnel. This qualification process will identify the solution set(s) best of breed currently available that can immediately meet mission needs. This overall objective will be accomplished via one or more iterations of testing before a final procurement decision is reached. The objectives listed in this section are focus areas of interest for the Government.

A solution should include a tactical Mesh network that will connect to the existing compute and store edge nodes. The Mesh technology and tactical edge node will act as a single platform and utilize terrestrial and non-terrestrial (i.e. air, and space) methods to provide dynamic connectivity to cloud and Internet Protocol (IP) connected platforms across the globe.

3.1. Project

3.1.1. Provide technical solutions that meet the ACP-E technical objectives listed in section 3.2

3.1.2. Leverage the fielded Government Furnished Property (GFP) technical baseline as referenced in Table 1 below

3.1.3. Provide three solutions for operational evaluation by users adhering to notional architecture depicted in Figure 1, Figure 2, and Figure 3 below

3.1.4. The third solution will not use Mesh radios (Figure 3) but will connect to an AF controlled cloud instance.

3.1.5. Provide support for operational evaluation

3.1.6. Provide technical architecture and List of Materials (LOM)

3.1.7. Provide updated information for the set up and operation of the proposed solution

3.1.8. Provide proof of Supply chain risk management IAW most current version of the NISTIR

7622 and DoDI 5200.44

3.1.9. Provide evidence that proposed solution does not go EOS/EOL earlier than two/four years respectively after CA

3.2. Mesh Radios

3.2.1. The tactical communications system shall support a minimum aggregate throughput of 100 Mbps across a 10-mile radius

3.2.2. Leverage the fielded ACP-E technical baseline

TDC GFP Hardware Software 1 Management Laptop Panasonic Windows 11

1 ACP

PacStar 451-NR (Servers) Redhat (Hypervisor): hosts virtual software listed below

PacStar 451 (Servers) Cisco C8000v (Router) PacStar 446 (24 Port Switch) Aruba VMC (NIPR WiFi) PacStar 444 (10 Port Switch) Forcepoint NGFW (Firewall) PacStar 448 (10Gb Switch) Windows Server (Domain Controller) PacStar 463 (RoIP SIPR only) Wave (SIPR RoIP)

Redcom Sigma Core (VoIP) ACAS (Security Scanning)

ESS (HIPS)

IQ-CORE (System management / Syslog) File Server

1 FACT PacStar 451 (Servers) Cisco C8000v (Virtual Router) PacStar 446 (24 Port Switch) PacStar 444 (10 Port Switch)

Table 1: GFP HW/SW list

3.2.3. Be capable of iterative expansion and extension to support additional users, ad hoc network functions, and coverage areas leveraging the fielded technical baseline and integrating key capabilities demonstrated by existing systems to minimize planned obsolescence.

3.2.4. All transit cases must be 66 lbs (30 kg) less to enable worldwide transport and checkability on commercial aircraft (Objective)

3.2.5. Be worldwide power compatible with autosensing

3.2.6. Mesh radios will be certified MILSPEC810

3.2.7. Encryption between the radios should be NSA approved

Figure 1

Figure 2

Figure 3

4. Procurement The Contractor will establish a B-table to procure the existing ACP system configuration during a rapid prototyping phase and a B-table to procure any Government-approved enhancements or deviations to the existing technical baseline.

5. Meetings Meetings between the Government and the Contractor will occur as required or requested by either of the parties. The intent of the meetings should be primarily focused on readiness for the test event(s) and the planning activities as required. Test specific conferences will be occurring throughout the Period of Performance and the contractor will be invited to attend at their own choosing.

6. Operational Evaluation If requested, the Contractor shall participate and contribute in the Planning, to include providing to the Government products and data. The Contractor will participate in Technical Review Boards, Safety Review Boards, Evaluation Readiness Reviews, Evaluation Execution, Data Analysis and Reporting as directed by the Government. The Government will require all data within this system associated with Government work/evaluation.

The Government will be performing an operational evaluation on the ACP-E solutions to include, but not limited to the overall capability, connection feeds, the flow of data, and the ability to perform in a disconnected operation, and utilize multiple backhauls (ex. 4G/5G, Starshield, MilSATCOM), Mesh radios. The contractor shall allow the Government to tap the system which will allow for active monitoring if requested. The contractor shall abide by all planning and execution guidance provided by the government. Evaluation will include functional user evaluation along with the potential for additional production testing.