(U) WL Enterprise SOO Finalv 24 Mar 2026.docx

UNCLASSIFIED

STATEMENT OF OBJECTIVES

FOR

Follow-On Mobility Enterprise Connectivity

24 March 2026

1. WL Enterprise Connectivity

1.1 Introduction

Program Executive Office (PEO) Mobility (WL) is prioritizing efforts to connect the fleet with the goal of providing secure communications in pursuit of global command and control. Mobility will produce a platform-specific connectivity roadmap aligned with the Department of the Air Force (DAF) Battle Management Network (DAFBN). The increasing global threats face the United States require a faster mechanism for WL to acquire, install, and sustain across the current and emerging mobility fleet. WL continues to evolve the transport and refueling fleet into a modernized force with continuously evolving advanced and secure connectivity requirements essential in a modern fight.

1.2 Scope

While Mobility Air Force (MAF) connectivity requirements are common across the fleet, integration remains inherently platform-specific due to variations in aircraft architectures, certification pathways and sustainment constructs. To mitigate execution risk and enable scalable deployment, WL requires a disciplined, repeatable approach to visualize, validate, operationalize and rapidly scale enterprise connectivity capabilities in alignment with operational timelines.

WL will pursue an incremental acquisition approach focused on fielding common requirements across the MAF based on USAF prioritization and operational needs:

· Increment 1: Hybrid SATCOM (HST) Prototyping

· Increment 2: Prototyping with NIPR/SIPR connectivity

· Increment 3: Prototyping with emerging next generation DAFBN integration

· Increment 4: Follow-on prototyping of connectivity requirements and long-term training and sustainment of existing requirements

The initial increment is focused on installation of foundational HST capabilities for connectivity and in reducing technical and programmatic risk by identifying integration challenges, certification constraints, and critical data gaps. This initial increment will provide “proof of concept” for development government-owned technical data packages (TDPs), maximizing future competition, and establishing a foundation for follow-on integration and sustainment activities without dependence on vendor-owned intellectual property. Comment by Debbie Naguy: @Ralph E Lemaster Will probably need additional clarity on phased acquisition approach. Phase 1 will be Starshield prototype, Phase 2 Starshielf prototype w/NIPR/SIPR connectivity, Phase 3, HST prototype w/Janus or NEXUS. Also want to follow prototype will installations. Comment by Kelly Hough Gilbert: @Ralph E Lemaster are we mixing acquisition phases with requirements?? Is the intent to limit this SOW to use the above??

The results of the “proof of concept” inform the strategy for transitioning the evolving communications requirements to a production-capable environment to be utilized by the entire MAF. The overarching requirements will be focused on the following areas: Non-recurring Engineering, Installation, Training, and Sustainment.

The second increment of this approach focuses primarily on prototyping and installations with NIPR and SIPR connectivity. The third increment will continue prototyping and installations with Phalanx Griffon capabilities, full integration with DAFBN, and production installations. The fourth increment focuses on emerging connectivity requirements and long-term training and sustainment of existing requirements. Comment by Debbie Naguy: @Ralph E Lemaster I would not put the statement about not relying on OEMs, OEMs might bid on the contract, this would drive a protest. Comment by Kelly Hough Gilbert: @Ralph E Lemaster I tweaked the language

The end goal is a standardized approach to development of enterprise requirements, governance, and acceptance criteria while enabling modular, platform-tailored implementation. This approach delivers consistent outcomes across the mobility enterprise while preserving the flexibility to execute efficiently on each platform.

This Statement of Objectives (SOO) will be capable of accommodating varying degrees of technical/requirements maturity to enable rapid near-term execution while preserving long-term strategic agility by tailoring contract types to mission priorities, optimizing competition, compliance, and resource sharing. We will provide an enterprise approach to procure, install, certify, and scale common requirements and/or upgrades across multiple aircraft platforms utilizing the following key tenants:

· Common requirements - Common solutions - Unique implementation

· Centralized oversight – decentralized execution

· Modernization efforts must include aircraft connectivity to DAFBN

· Varied mission sets executed across MAF fleets will drive different connectivity prioritization and implementation plans and not every design will have the same full, permanent capabilities installed

This SOO includes the following activities (but not limited to): Comment by Debbie Naguy: @Ralph E Lemaster I think you got this, but each one of these activities need to have a dedicated section Comment by Debbie Naguy: @Ralph E Lemaster Probably need to identify which will be GFE such as products from C3BM (TACkits, Janus, Nexus). Need to confirm PG plans of fund these items. Once note, TACKit can be procured with Starshield....so that needs to be figured out.

· A-Kits Production

· B-Kits Production

· Support Equipment Kits Production

· Shipping of material

· Installation/modification of aircraft e.g. FSR, CFT, etc. Comment by Debbie Naguy: @Ralph E Lemaster In this section, want to provide a minimum thru put of 12 aircraft a month but may want to have contractor provide max aircraft per month for each phase of installation. Can they accelerate if necessary and if so how will they perform.

· Provision of spare parts

· Sustainment activities

· Engineering (including non-recurring engineering [NRE])

· Training Services

· Over & Above activities

1.3 Language

The language for all correspondence and deliverables pertaining to this project shall be English.

1.4 Service Location

MAF connectivity installations may be performed at USAF installations, Contractor facilities and other operational sites, as required.

1.5 Requirements Classification

The Contractor shall follow all requirements and perform all actions defined in the SOO and follow-on requirements.

2. Engineering, Design and Development The contractor shall plan for and develop design for new, developmental, existing and/or modified hardware and software; and support all design activities and cybersecurity as defined in follow-on requirements. The contractor shall perform disciplined technical planning, coordination, and execution of engineering to ensure product development includes strict application of technical metrics and processes, incorporating maintainability and supportability into the design. The contractor shall provide technical documentation and data models, updates to technical orders, drawings, manuals, engineering tools, and support all technical reviews and airworthiness tasks such as defined in follow-on requirements. Comment by Debbie Naguy: @Ralph E Lemaster Need to include updating technical orders, drawings, and manuals.

3. Architecture

3.1 Open Architecture

The contractor shall ensure its designs incorporate Government Referenced Architectures that enable capabilities and allow for integration across multiple platforms, as defined in follow-on requirements.

3.2 Intellectual Property/Data Rights

The preference for data associated with the deliverables under this contract, including Technical Data Packages (TDPs), software, and related documentation, is that there is no limitation on use, modification, reproduction, release, performance, display, or disclosure.

3.3 Associate Contract Agreement

The contractor may be required to enter into Associate Contractor Agreements (ACAs) for any portion of the contract requiring joint participation in the accomplishment of the Government's requirement in accordance with (IAW) AFFARS IG 5317.9000.

The ACAs shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources are essential to the MAF, which shall ensure the greatest Comment by Debbie Naguy: @Ralph E Lemaster Recommend replacing ABMS with mobility platforms.

degree of cooperation for the development of the program to meet the terms of the contract.

ACAs shall include the following general information:

1. Identify the associate contractors and their relationships.

2. Identify the program involved and the relevant Government contracts of the associate contractors.

3. Describe the associate contractor interfaces by general subject matter.

4. Specify the categories of information to be exchanged or support to be provided.

5. Include the expiration date (or event) of the ACA.

6. Identify potential conflicts between relevant Government contracts and the ACA; include agreements on protection of proprietary data and restrictions on employees.

The contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government.

All costs associated with the agreements are included within the individual awards for which they apply to. Agreements may be amended as required by the Government during the performance.

4. Program Execution

4.1 Program Management

The contractor shall provide for planning, coordination, organization and execution of all program management tasks to include, but are not limited to, development, documentation, reporting of all Program Management processes, products, and artifacts;

financial and contract performance documentation and reporting; configuration management and data management, including risks and issues management; cost and schedule tracking and reporting; subcontract management and reporting; sustainment planning. Five areas of effort, but not limited to,: Non-Recurring Engineering (NRE), material, integration, test and demonstration.

4.2 Systems Engineering

The contractor shall perform disciplined technical planning, coordination and execution of systems engineering as defined in follow-on requirements.

4.3 Security Management

If applicable, the contractor shall comply with the security requirements specified in the contractor’s DD Form 254, Contract Security Classification Specification.

4.4 Installation / Modification of Aircraft

The Contractor shall perform MAF Connectivity kit installations in accordance with applicable TCTOs.

The Contractor shall work with the applicable SPOs and Air Mobility Command to prepare Memorandum of Agreement (MOA) for hangar and field unit support requirements.

The Contractor shall prepare and coordinate aircraft handover protocols prior/post installation work for each aircraft.

Series Kit installation shall be conducted simultaneously, in accordance with the USAF installation schedule.

The Contractor will be required to maintain a minimum throughput production rate. Aircraft availability and deployment schedules will impact the USAF installation schedule and installation locations throughout the duration of the Contract; therefore, the USAF installation schedule will be a living document discussed during regular touchpoints with Contractor.

The Contractor shall remove and turn-in the legacy components to USAF in accordance with the local unit procedures. The Contactor shall support field units with the packaging of legacy components in serviceable condition (Condition Code “D”). The Contractor shall support field units with the turn-in of CCI in accordance with COMSEC disposition procedures.

Contractor shall perform all required ground tests with own personnel.

The contractor shall perform all MAF Connectivity Acceptance Check Flight maintenance preflight IAW the appropriate TOs and provide support to the USAF aircrew in the performance of their preflight.

The contractor shall support USAF crews (as required) in performing an Acceptance Check Flight

In case USAF experiences problems with the new MAF Connectivity components during first flight after the Acceptance Check Flight, the contractor shall provide services to remedy the problem at the aircraft current location utilizing a contract field team (CFT).

The contractor shall document additional maintenance actions related to aircraft delivery.

4.5 Installation Kits Production

The Contractor shall produce MAF Connectivity A-Kits, which consist of all permanently installed components, B-Kits, which consist of non-Controlled Cryptographic Item (CCI) and TDP specified LRUs, and support equipment kits.

A detailed breakdown of the MAF Connectivity A-Kits, B-Kits, and support equipment kits are provided in the Technical Data Package (TDP), drawings as per SOO and corresponding Bills of Materials (BOM). The Contractor shall include all consumables listed in the BOMs. Contractor shall assemble MAF Connectivity A-Kits, B-Kits, and support equipment kits into fully functional MAF Connectivity Installation Kits.

4.6 Shipping of Material Comment by Jeff Meserve: @Ralph E Lemaster If all we are talking about here is shipping of kits...perhaps 5.5 can be “Modification Kits”...with two sub sections; 5.5.1 “Kit Production” and 5.5.2 “Shipping of Kits” (or something like that).

The Contractor shall package kits (and individual material, if required) in accordance with AWSTM-D-3951, Commercial Packaging, or MIL-STD-2073-1, Standard Practice for Military Packaging, and ANSI/ESD S20.20-2021, Protection of Electrical and Electronic Parts.

The Contractor shall mark the packages for shipping and storage in accordance with MIL-STD-129, Military Marking for Shipment and Storage. Each shipping container shall clearly display the kit name, kit NSN, S/N and Contract and Call-Off Purchase Order number on the outside of the shipping container.

The Contractor shall ship kits to the MAF Connectivity Installation locations defined in SOO, as requested by USAF and notify the USAF indicated POC at the location.

If a shipment is lost or misplaced during transit, the Contractor shall immediately notify USAF.

The Contractor shall provide the USAF indicated POC via email with the commercial shipping documentation or provide the shipping information on a DD Form 1149 Requisition and Invoice/Shipping document for each shipment.

The Contractor shall have the capability to ship to all other CONUS locations and to ship individual material (not kitted). Other CONUS locations or not kitted material shipping will result in an amendment of the Contract List of Services or be treated as per SOO.

4.7 Provision of Spare Parts Comment by Jeff Meserve: @Ralph E Lemaster My previous comment is really a setup for this comment.

Recommend one section for Sustainment (e.g., 5.6 “Sustainment”), and several sub-sections, on of which is “Supply Chain” (5.6.1) which is a subset of Sustainment. Initial provisioning/sparing is part of), Interim Contract Support for spares, SCRM, DMSMS, etc….all part of Supply Chain. (they can be 4-digits (e.g., 5.6.1.1, etc).

Depending on how far we want to go with Sustainment...there could be all the elements of product support (supply chain plus 11 others). Not sure that is necessary here though?

Maybe since these are essentially spares being installed on the aircraft...perhaps supply chain is enough.

@Trixie Renee Brewer – your thoughts?

The Contractor shall provide spare parts for the MAF Connectivity installation kits (Spare Parts List), as required by USAF. Specific identification of required spare parts will be listed in each individual follow-on effort. The shipping for those parts shall be handled in accordance with SOO.

4.8 Training Services

As specified in follow-on requirements, Contractor will establish and provide both operator and maintenance training as applicable for specific installations. Scope of training will depend on SPO/AMC requirements per type of capability installation.

4.9 Over and Above (O&A) Activities

Contractor may be asked by USAF to provide O&A support for repairs and maintenance activities within the scope of this project, including:

1. Supply of repair parts, material, tools and equipment to support the over & above maintenance and repairs for this project.

2. Engineer and technician support on maintenance and repairs.

Those O&A repair activities shall be provided on a case-by-case basis. Upon request by USAF, the Contractor shall provide a separate proposal within fifteen (15) calendar days detailing a breakdown of number of labor hours and hourly rate in accordance with the contract, material and handling charge in accordance with the contract, TAT or lead time for USAF evaluation and approval before any Purchase Order issuance.

The individual work scope, lead time, deliverables and acceptance criteria shall be referenced in the corresponding Purchase Order.

Any O&A activities not covered in advance by NSPA Call-Off Purchase Order are to be considered as unauthorized work and shall not be reimbursed.

4.10 Exclusivity Agreements

Contractors shall not require other contractors or entities to sign an exclusivity agreement that could prevent further activity within the WL portfolio.

4.11 External Relations

Due to the increased media attention on WL and the high potential for adversaries to target/collect program data, properly applied Operations Security (OPSEC) measures must be considered to protect sensitive unclassified information.

Even if information is published, it may not have been approved for public release.

Do not confirm, deny or forward classified information that appears in the media via unclassified channels. Public release requests must be submitted to the AFLCMC office 45 days prior to requested release date and must be approved by AFLCMC Public Affairs Officer and Security. To request a public release approval, submit a DD Form 1910, proposed material and partner approvals to the WL Program Manager for review.

5. Studies, Analyses and Demonstrations Special studies, analyses, and demonstrations shall be performed as defined in follow-on requirements.

UNCLASSIFIED