SEWOL CNS Excerpts - Final.docx

UNCLASSIFIED

SPACE ELECTROMAGNETIC WARFARE OPERATING LOCATION (SEWOL)

CAPABILITY NEEDS STATEMENT (CNS) EXCERPTS

JULY 2025

(U) Executive Summary

(U) This CNS identifies capabilities and attributes required of the cloud-based Space Electromagnetic Warfare Operating Location (SEWOL) to meet operational needs. The integrated SEW solution will enable USSF SEW forces to not only compete, but thrive in a contested degraded operations (CDO) environment, during both high end conflict and peacetime.

(U) Operational Context

(U) SEWOL will be the USSF’s cloud-based application used to Plan, Task, Manage, Control, and Perform all tasks necessary for tactical planning, tactical tasking, collaboration between locations and systems, and execution of tasked SEW missions. Distributed operators can use the SEWOL to task available resources, and execute effects, and the operators will see what other operators are doing and relevant resource status in near real time.

(U) SEWOL will serve as the Command and Control (C2) interface across the SEW enterprise. SEWOL will need to have the ability to integrate with many SEW systems, to include Remote Modular Terminal (RMT), Bounty Hunter, Counter Communications System (CCS) Meadowlands (MDLS), and future SEW systems.

(U) The users of the SEWOL system will include SEW weapon system operators and mission planners within various tactical and strategic roles.

(U) Capabilities Needed

(U) The SEWOL software application(s) to be developed will need to be capable of marrying the interaction between user, varying EW hardware platforms, and communication architecture to ultimately translate into EW effects being employed as intended on validated targets. The software needs to be reliable, flexible, sustainable, and easily upgradable.

(U) SEWOL should strive for the utilization of an open software platform in order to improve access for development, upgrades, and sustainability. Consideration should be made to leverage commercial off the shelf (COTS) and/or government off the shelf (GOTS) products. The software must be designed to be scalable to support a variety of operators and use cases. Being a cloud-based solution, SEWOL should be optimized to include a wide spectrum of hardware and software interfaces.

(U) SEWOL needs to provide a Common Operating Interface (COI) in the form of a graphical user interface (GUI) which serves as the system-to-system interface between SEWOL and multiple types of connected SEW systems. The SEWOL COI shall define the means by which SEWOL exchanges messages between itself and connected SEW systems.

(U) The SEWOL COI will serve as a unifying interface for operators to efficiently manage their systems, including controlling all tasks necessary for engagement planning, tasking, and execution of theater operations for connected SEW systems. The COI will need to support a scalable number of SEW systems.

(U) SEWOL needs to provide a Common Operating Picture (COP) in the form of a GUI which displays relevant real-time and historical information from the repository such as connected SEW systems, targets, SEW tasking, ongoing SEW activities, network availability, system status, etc. The SEWOL GUI will allow users to create and share customized user defined operational pictures.

(U) SEWOL will use a central repository as the authoritative source for SEW operational data, including all system and mission data such as operational and tactical tasking, system status data, targeting package data, etc. SEWOL central repository will manage the data interface between SEWOL’s internal applications as well as between SEWOL and external data sources including but not limited to UDL, Warp Core, AWS Cloud, the intelligence community, or other databases.

(U) Remote operations performance will rely heavily on the communication architecture. The SEWOL software will need to be network agnostic and be able to perform its function across varying communication solutions to ensure successful communications in any environment.

(U) SEWOL will provide a Tactical Command and Control (Tac C2) application for mission planning tasking and execution monitoring. The Tac C2 will need to provide the capability for weapon target pairing based on higher strategic tasking (regional C2). Tac C2 should enable automated and remote operations of SEW systems, and provide automated and manual scheduling of SEW resources.

(U) Interoperability

(U) The SEWOL and its components will be designed with an open-architecture, open standards, and machine-to-machine (M2M) interface approach to facilitate interoperability with the SEW enterprise and rapid on-boarding of new capabilities, C2 applications, and SEW systems. The program will promote hardware-agnostic, cloud-based platform as a service (PaaS), infrastructure as a service (IaaS), and data as a service (DaaS) methodologies to support a continuous integration/continuous development (CI/CD) pipeline to develop the SEWOL modules and capabilities.

(U) SEWOL will develop an open standard remote EW systems interface definition jointly with the SEW system developers. A software development toolkit will be provided for future external systems to develop, integrate, and test with models of the enterprise, databases, and interfaces. An open-standard enterprise messaging approach will be used to facilitate communication within SEWOL and between systems.

(U) Requirements Management

(U) The SEWOL development will employ agile software methodologies for requirement fulfillment, incorporating user feedback through the quickest approved process, and to respond to emerging needs. The program will use a DevSecOps approach to “bake in” security and facilitate early deployment with a common cloud-based platform. The CI/CD pipeline will enable quick detection of issues, automated code commits, integration, and testing with quicker fielding of capabilities via a continuous Authority to Operate (ATO).

(U) A minimum capability definition will be provided to the developer at the outset and this will be the initial goal for the first phase of the program. This will be continually refined with user feedback, as well as the associated acquisition Deltas during sprint planning, reviews and demonstrations, and retrospectives. A user agreement will be developed and will further elaborate on specific roles and processes to ensure commitment and active continuous engagement occurs throughtout the software development process.

(U) This CNS should be revisited bi-annually to capture updates and changes to the capability needs.

UNCLASSIFIED