SEWOL Program Definition - Final.docx

(U) SPACE ELECTROMAGNETIC WARFARE OPERATING LOCATION (SEWOL)

(U) SEWOL PROGRAM DEFINITION

(U) 25 JULY 2025

(U) UNITED STATES SPACE FORCE (USSF)

(U) SPACE SYSTEMS COMMAND (SSC)

UNCLASSIFIED

(U) COMBAT SYSTEMS PROGRAM OFFICE

UNCLASSIFIED

(U) TABLE OF CONTENTS

(U) Program Definition

(U) Introduction and Background

(U) SEWOL will enable SEW operators to manage, control, and perform all tasks necessary for tactical planning, intelligence preparation of the battlespace, tactical tasking (assignment of engagements to individual EA systems within SEWOL control), collaboration between IC, Regional C2 of other SEW Systems, and execution of tasked missions. SEWOL will provide a cloud-based set of applications that provide command and control of remote and local EW weapons platforms, collaborative tools to enable effective tactical execution, and a single authoritative data source.

(U) Figure 1 below illustrates a notional SEWOL operational view (OV-1) depicting the SEWOL cloud applications, primary and alternate common operating locations (COLs), Combined Space Operations Center (CSpOC) or other Regional C2 node, C2 Database-as-a-Service (DaaS) and SEW systems including Remote Modular Terminal (RMT), Bounty Hunter, and Counter Communications System (CCS) Block 10.3 (Meadowlands). RMT is a ground-based SEW system designed for electromagnetic support and electromagnetic attack against SATCOM. RMT is on a smaller unmanned platform optimized for low-cost and large-scale deployment and autonomy to operate in a SECRET network. Bounty Hunter is a ground based system for electromagnetic support and identification and geolocation of RF interference, and operates in a TS/SCI network. Meadowlands is a ground-based SEW system specifically designed to reversibly deny, disrupt, and deceive adversarial SATCOM. It is a trailer-mounted system operated remotely over a TS/SCI network. SEWOL will interface and provide C2 capabilities for RMT initially, then Bounty Hunter, Meadowlands, and future SEW systems.

(U) Figure 1 Notional SEWOL Operational View - 1

(U) For the purpose of this document, “System” refers to the SEWOL and its applications running on a cloud environment. “Repository”, generically, refers to the SEW data repository. “Government” refers to the team of Space Systems Command (SSC)/SZWC Program Office (PO), SETA, and FFRDC personnel. “Operator” refers to the Government users that will use the SEWOL system for SEW missions.

(U) There will be two physical locations – a Contractor System Integration Laboratory (SIL) and a Government Common Operating Location (COL). The Government COL will be the United States Space Force’s (USSF’s) primary common operating location for planning, tasking, and execution of SEW operations. The cloud environment and physical locations will collaborate to serve the following purposes:

1. (U) Initial development

2. (U) Operator interaction and feedback as part of the agile process

3. (U) Demonstration of SEWOL operational capabilities

4. (U) High resiliency and operational flexibility

(U) SEWOL Use Cases

(U) This section presents notional SEWOL use cases:

(U) A user accesses the SEWOL unclass website for information related to the program, such as introduction, points of contact, and frequently asked questions (FAQ) about how to get an account. A user requests an account by filling out a form with a valid email address and will need to have a Common Access Card (CAC) or an External Certificate Authority (ECA) card.

(U) A SEWOL user submits account requests, problem tickets and feedback to the SEWOL help desk.(U) Once an account is granted, the user will only be allowed access to SEWOL functions based on Role Based Access Control (RBAC) on each of the instances in Unclassified/SECRET/TOP SECRET Sensitive Compartmented Information (TS/SCI) environments. For example, a SEW operator would have access to COI, SEWCOP, and Tac C2; a Tac C2 planner would have access to SEWCOP and Tac C2; and the administrator would have access to SEWCOP and a network monitor.

(U) A SEWOL user can access the instruction and manual for the SEWOL online. The web interface allows users to access training material and tutorial if available.

(U) Operators in a Contractor SIL or a Government COL can log in to SEWOL to plan and conduct SEW missions as well as configure and manage connected SEW systems. Operators in an alternative location who have access to the SEWOL application can also access the same capabilities. Each user will see a persistent display in the same state the user was in before the user logged off. Furthermore, users can share the display interactively with other users remotely for task approval, monitoring, help desk debugging, and instructor-led training. [Note: Task approval may involve reviewing tasking orders prior to SEW system execution.]

(U) SEWOL operators access the system from the Government COL and can perform EW operations as the designated tactical C2. To meet CCDR priorities for flexibility in its mobility and maneuverability, SEWOL will shift operations from the Government COL to a network of small, dispersed nodes controlled from a SEWOL either in theater or from one of the SEW garrison locations, with the possibility of alternate sites functioning as backups.

(U) SEWOL receives mission tasking via machine-to-machine interface to Regional C2. SEWOL operators, or SEWOL LNO based in the AOC, approve the mission tasking or augment with additional data as necessary. SEWOL generates several proposed schedules / COAs with different optimization strategies for conducting the mission tasking, including the concept of orchestrating/coordinating effects across multiple connected SEW systems. SEWOL’s weapon target pairing algorithm considers several factors including but not limited to existing tasking, SEW locations, SEW capabilities, desired effect on target, and transponder beam footprints. Operator approves schedule associated to preferred COA, and SEWOL builds the appropriate commands and transmits tasking to relevant SEW systems.

(U) During execution, operators monitor SEW fleet status and tasking execution status in real time. If a SEW task fails, SEWOL automatically reattempts the task or re-assigns the task. SEWOL automatically used available SEW data or operator input to adjust SEW tasking to ensure effectiveness.

(U) SEWOL Product Vision

(U) The software releases (including the end product) must fall within the scope of the Product Vision described in the following statement:

(U) The SEWOL System will empower SEW operators to efficiently manage a globally distributed network of SEW systems that are resilient and scalable. This system will enable a small team of operators to oversee and execute automated tactical command and control across hundreds of globally deployed SEW systems simultaneously. These operators will be able to engage with hundreds of adversary transponders and thousands of signals of interest across various RF bands. The modular, cloud-hosted, and accessible system facilitates remote operations and real-time decision-making throughout the Electromagnetic Spectrum Operations (EMSO) enterprise. In contrast to the current model, which requires a large crew to manage collocated systems, SEWOL integrates comprehensive counter-SATCOM EMSOC2 warfighter capabilities with fewer resources, ensuring continuity of operations from distributed nodes.

(U) Key Milestones

(U) The government is considering the following milestones for the SEWOL effort.

(U) Agile methodology will be used for system development with several notable milestones on the product roadmap as follows:

· (U) Minimum Viable Product (MVP): Pre-operational version of SEWOL usable by early customers to provide feedback for future product development

· (U) Contractor System Integration Lab (SIL) Completion

· (U) Minimum Viable Capability Release (MVCR): Initial operational capabilities described in the provided MVP Functions Document.

· (U) Capability Release i (CR-i): One of the Capability Releases (CRs) following the MVCR that incrementally add capabilities to reach the final operational capabilities. Expected quarterly post MVCR

· (U) Capability Release n (CR-n): Final operational capabilities 24 months post ATP that meets all program objectives

(U) Agile Process

(U) The SEWOL effort will be completed in a team-based agile environment. The Contractor will create and maintain system and capability roadmaps, project plans, and product and release backlogs that will be the basis for the Contractor’s work. The Government Program Manager (GPM) will specify a high-level product roadmap to the Contractor product owner(s) to support preparing and prioritizing the product backlog. The Contractor will develop estimates and establish acceptance criteria for Capabilities and related work items. These acceptance criteria will specify expected functionality for each work item (Capability, Feature, Story), as well as any non-functional requirements that must be met in the development of the story. The Contractor product owner, supported by subject matter experts (SMEs) and business analysts, will determine whether acceptance criteria have been satisfied for the user story. The Government and the Contractor product owners will closely collaborate and come to an agreement on acceptance criteria for increment features and will determine whether acceptance criteria have been satisfied for the feature. The Contractor will ensure an appropriate coverage of automated testing will be implemented.

(U) The Contractor will use traditional agile processes such as Increment Planning and Reviews (IPR), Increment Functionality Demonstrations (IFD), and Sprint Planning and Reviews (SPR).

(U) The Government PM will use IPR to evaluate system design and assess the Contractor’s readiness to implement modifications or upgrades in the subsequent increment.

Minimum Viable Capability Release Objectives

(U) The Contractor will meet the following objectives when delivering the MVCR capabilities of SEWOL

1. (U) At a minimum, the capabilities described in the MVP Functions Document have been demonstrated, operationally tested, and fielded.

2. (U) Preliminary Technical Manual Verified.

3. (U) Initial Type-1 training complete.

4. (U) Contractor SIL with dedicated connections to TS/SCI and SECRET classified clouds complete and demonstrated.

(U) CR-n Objectives (End State)

(U) The Contractor will meet the following objectives when delivering the end state capabilities of SEWOL:

1. (U) Completion of all aspects of the SEWOL Strategic Product Roadmap.

2. (U) All SEWOL functions have been demonstrated, operationally tested, and fielded.

3. (U) Final Technical Manual Verified

4. (U) Final Type-1 training event complete

5. (U) Final OCD

6. (U) External ICD between SEWOL applications and future SEW systems

(U) Data Management (DM)

(U) The Contractor will establish and maintain a secure Integrated Digital Environment (IDE) on Platform One for hosting all technical data and computer software produced in the performance of this contract. The purpose of the IDE is to create a seamless, collaborative data environment for the Contractor and Government PO team, which contains all pertinent data about the project throughout its development and delivery.

(U) Systems Engineering, Integration & Test

(U) Modular Open Software Approach

(U) The Contractor will use modular software design, open standards, and interoperable Machine-toMachine (M2M) interfaces to support future growth and mission evolution.

(U) DevSecOps Environment

(U) The Contractor will design, implement, test, and deploy the system on a cloud development, security, and operations (DevSecOps) environment with computer and network hardware in physical facilities, such as Platform One and ODIN.

(U) The Contractor will configure and maintain a DevSecOps environment for SEWOL applications.

(U) The Contractor will use a Continuous Integration and Continuous Delivery (CI/CD) toolchain to continuously enhance automation and security.

(U) Interfaces

(U) The Contractor will lead the definition and documentation of the SEWOL internal ICDs including leading IPT meetings with the Government PO and other stakeholders.

(U) The Contractor will develop and deliver all internal ICDs..

(U) The Contractor will lead the definition and documentation of the SEWOL external ICDs listed below including leading IPT meetings with the Government PO and other stakeholders.(U) The Contractor will develop and deliver all external ICDs , such as the following:

1. (U) SEWOL to RMT

2. (U) SEWOL to Bounty Hunter

3. (U) SEWOL to CCS Meadowlands

4. (U) SEWOL to future Electromagnetic Warfare (EW) weapon systems

5. (U) SEWOL to Regional C2 system(s)

6. (U) SEWOL to Intel databases

7. (U) SEWOL to Unified Data Library (UDL)

8. (U) SEWOL to Warp Core

(U) The Contractor will use real operational SEW systems, or external interface emulators for integration testing with external systems if available.

(U) The Contractor will support external systems to test integration with the SEWOL.

(U) Integration, Test, and Evaluation

(U) Development of Test Plans and Procedures

(U) The Contractor will test (including integration, qualification testing and regression testing) and maximize automation.

(U) RMT Integration and Test

(U) The Contractor will observe all RMT contractor formal testing to understand RMT system design and functionality when the contractor is not restricted from attendance by the RMT contractor and/or the Government.

(U) The Contractor will participate in RMT contractor remote interface testing to allow smoother integration to SEWOL.

(U) The Contractor will lead integration and testing of RMTs into the SEWOL architecture.

(U) The Contractor will collaborate with the RMT team on the development of the RMT-SEWOL communications architecture, security, and network design.

(U) The Contractor will support an Authorization To Connect (ATC) effort to interface with RMT.

(U) Government-Led Integrated Test

(U) The Contractor will support Integrated Test activities at the direction of the Government. Support activities include but are not limited to: addressing the Government’s feedback throughout agile development; assisting the Government DT/OT organizations in development of DT/OT plans and procedures; addressing the Government’s feedback during the Contractor testing and the Contractor’s Deficiency Report Review Board (DRRB); providing support for DT/OT-related activities; and cohesively working with the Government Deficiency Review Board (DRB) to resolve identified deficiencies in a timely and efficient manner.

(U) System Security Engineering

(U) Program Protection

(U) The Contractor will develop and comply with a Program Protection Plan

(U) Cloud and Network Infrastructure

(U) The Contractor will provide networking, security, and infrastructure support for connectivity to GFE NIPRNet, SIPRNet, and JWICS at the Contractor SIL.

(U) The Contractor will design a resilient architecture that ensures continuity of operations in alignment with the DT-SEW CONOPs.

(U) Cross Domain Solution (CDS)

(U) The Contractor will architect and implement the System to enable TS/SCI-to-SECRET and SECRET-to-TS/SCI data transfer, such as via UDL and WarpCore.

(U) Security Classification Domains

(U) The Contractor will design the System with instances deployable in the TS/SCI and SECRET classification domains.

(U) The Contractor will design the TS/SCI instance of the System to include all data from SEW systems at the TS/SCI and SECRET classifications.

(U) The Contractor will design the TS/SCI instance of the System to be able to command and control, and monitor SEW systems at the TS/SCI and SECRET classification levels.

(U) The Contractor will design the cloud-based SECRET instance of the System to be capable as a stand-alone system to independently command and control, and monitor SECRET SEW systems.

(U) The Contractor will design the System as software and hardware agnostic allowing the System to migrate to an alternative platform with minimal efforts.

(U) The Contractor will design the System to be deployable on a local network (i.e., a laptop computer or other edge computing platform). [Note: This capability is an End State objective. Motivation is for the System to have the capability to operate in an ad hoc network, access to limited local databases and without connecting to the cloud.]

(U) The Contractor will design and implement the System training mode in classified and unclassified environments.

(U) Cybersecurity

(U) The SEWOL applications running on P1/ODIN will use the P1/ODIN’s umbrella Authorization to Operate (ATO). The Contractor is expected to obtain a Certificate to Field (CtF) for the SEWOL applications to get an ATO.

(U) The Contractor will follow a Pl CtF Checklist to obtain CtF.

(U) The Contractor will address all issues in the source code identified by the P1’s industry standard testing tools, and document how the issues were addressed.

(U) The Contractor will obtain and maintain a CtF for the SEWOL applications running on Pl/ODIN annually.

(U) The Contractor will practice secured source code management to ensure the source repository is only accessible by authorized developers.

(U) The Contractor will provide integration of security processes and tools during development, operations, and sustainment to address vulnerabilities and cybersecurity threats IAW latest Application Security and Development STIG.

(U) The Contractor will protect classified information, data, and material in accordance with the EW Security Classification and Declassification Guide (SCDG).

(U) The Contractor will correct critical and fixable penetration findings beyond the RMF baseline controls, within the next PI or as directed by the Government.

(U) Risk and Opportunity Management

(U) The Contractor will develop, implement, maintain and document a Risk Management Plan (RMP) IAW Institute of Electrical and Electronics Engineers (IEEE) 15288.1.

(U) Systems Safety

(U) The Contractor will develop, implement, maintain, and document a System Safety Program through the System Safety Program Plan (SSPP).

(U) Data Rights

(U) The Government will retain Government Purpose Rights (GPR) to all technical data, including automation performed, Infrastructure-as-Code (IaC), Configuration-as-Code (CaC), and processes created under this contract, such as scripts related to automation.

(U) The Government will retain GPR to all data and information hosted in Contractor SIL, Cloud Service Provider, Platform One, ODIN, and web hosting environments. These include rights to logs, scans, analytics, and other data collected and generated by the Contractor and service providers.

(U) The Contractor will document all data with sufficient detail for third-party reuse of development, integration, testing, and deployment tools and environments.

(U) Technical Interchange Meetings (TIMs)

(U) The Contractor will hold and lead TIMs as needed at the direction of the Government to address and resolve technical and programmatic issues and to execute the program.

(U) Working Groups

(U) The Contractor will establish and implement standing or temporary Working Groups as required and per the Government's direction to execute the program.

(U) SEWOL Help Desk

(U) The Contractor will provide an unclassified user help desk that is manned 24/7 starting at MVCR.

(U) The Contractor will provide continuous application monitoring and continuous resource monitoring of SEWOL.

(U) Product Support

(U) The Contractor will ensure product support considerations are incorporated into system design.

(U) The Contractor will design, develop, implement, and maintain an Integrated Support Plan (ISP) that documents products and processes required to maintain system capabilities and comply with statutory and regulatory guidance.

(U) The Contractor will develop and deliver a Preliminary Technical Manual. This Preliminary Technical Manual will be updated for every CR..

(U) The Contractor will provide Type-1 training will occur at MVCR and subsequent CRs.(U) The Contractor will provide familiarization opportunities to support IT&E and other events as necessary. IT&E-supporting familiarization will include:

SEWOL Contractor System Integration Lab (SIL)

(U) The Contractor will build a Contractor SIL that has access to the Government NIPRNet, SIPRNet, and JWICS terminals.

(U) The Contractor SIL will be a physical lab with necessary infrastructure for development, integration, testing, and demonstration of the System.

(U) The Contractor SIL will be used to access the SEWOL applications on the cloud and demonstrate their capabilities.

(U) The Contractor will establish a dedicated direct connection from the Contractor SIL to the SEWOL DevSecOps cloud platform via the AMP facility.

(U) The AMP facility and ODIN will provide secure connectivity between the equipment at the Contractor SIL and the SEWOL applications running on ODIN.

(U) The Contractor will support the AMP to obtain an ATO and an ATC to interface with AWS, the Contractor SIL.

(U) The Contractor will use the Contractor SIL to support the MVP, MVCR, and SEWOL RMT integration activities.

(U) The Contractor will provision and maintain the Contractor SIL with furniture, computers, tech refreshes, patches, displays, networking equipment, encryptors, and necessary personnel workspaces for SEWOL functions.

(U) The Contractor will build the Contractor SIL in compliance with the applicable standards approved by the facility Accrediting Official (AO).

(U) The Contractor will maintain all required network connections.

(U) The Contractor will maintain and update cryptographic keys.

(U) The Contractor will allow the Government to access the Contractor SIL for reviews and demonstrations.

(U) The Contractor will procure Communication Security (COMSEC) equipment as required.

(U) The Contractor will support and enforce all cyber security requirements to obtain and maintain an Interim Authorization To Test (IATT) and/or ATO in accordance with National Industry Standards of Technology Special Publication (NIST SP) 800-53, Committee on National Security Systems Instruction (CNSSI) No. 1253, CNSSI No. 1253 Classified Overlay (with additional overlays where applicable), 16th Air Force Risk Management Framework (RMF) Knowledge Service Base, Department of Defense Instruction (DoDI) 8500.01, DoDI 8510.01, Intelligence Community Directive (ICD) 503 and Committee on National Security Systems Policy (CNSSP) No. 11 (National Policy Governing the Acquisition of Information Assurance (IA) and IA-Enabled Information Technology (IT) Products) and CNSSP No. 12 (National Information Assurance Policy for Space Systems Used to Support National Security Missions).

(U) Appendix A Acronyms

image1.png image2.png