SEWOL MVP Functions - Final.docx

UNCLASSIFIED

UNCLASSIFIED

SPACE ELECTROMAGNETIC WARFARE OPERATING LOCATION (SEWOL)

MINIMUM VIABLE PRODUCT (MVP) FUNCTIONS

JULY 2025

Summary Minimum Viable Product (MVP) defined herein represents the minimum capabilities / functions that are expected by Mission Delta 3 (MD 3) in order to use SEWOL effectively in support of the Space Electromagnetic Warfare (SEW) mission. These requirements are in relation to SEWOL being able to task and operate the Remote Modular Terminal (RMT) weapon system.

This description begins with the required functions in the major mission areas of Electromagnetic Support (ES) and Electromagnetic Attack (EA) and relationships between them.

Electromagnetic Support (ES) SEWOL must collect data on what tasks signals are on and off air, as well as what known and unknown signals are on air on relevant transponders.

· Ability to task the fleet to conduct ES tasks

· SEWOL must select a capable RMT for each task (based on transponders footprint, IDed through previous ES tasks)

· (Passive OPE (Operational Preparation of the Environment)) Electromagnetic Warfare Officers (EWO—operational crew member) will manually pair (using inclusion and exclusion) system for OPE, data will be used to drive future ES and EA tasks

· SEWOL will schedule higher priority tasks above lower priority tasks. Yield will not trump priority

· SEWOL will not drop ES tasks when it has a viable RMT for that task

· SEWOL must create an optimized schedule based on capable RMT

· ES: Schedule 95% ES tasks relative to ideal truth model

· EA: Schedule 90% EA tasks relative to ideal truth model Electromagnetic Attack (EA) Operators must be able to task a multitude of EA tasks to the RMT fleet. These tasks must effectively deny tasked signals, following all constraints and limitations applicable.

· Ability to schedule 1 Target signal per Software Defined Radio (SDR) with any technique (RMT Tactics, Techniques, and Procedures (TTP)).

· Transponder Translation Frequency (TTF) Probe

· TTF Probes will find open space and tie to specific Signal of Interest (SOI)

· Probe task separate from “EA” task

· TTF information tied to SOI, RMT agnostic

· TTF information (beam visible) tied to SOI & RMT pair

· Probe Required is modifiable within SOI detail card

· (Active OPE) Like ES, operators would perform TTF probes using Mission Type Order (MTO) for extended periods of time to establish visibility to transponder, SEWOL keeps data and does not erase when introducing new target deck

· Power Verification Probe (PVP) portion of probe task is NOT required

· SEWOL must schedule tasks based on MTO priority

· In the event of asset (RMT) fallout, re-optimization will ensure higher priority tasks are scheduled over lower priority tasks

· SEWOL will not drop EA tasks when it has a viable RMT for that task within hardware constraints (95%/90% scheduled ES/EA metric applies)

· SEWOL must task RMTs with up to 1 signal per SDR at once

· SEWOL must send all tasks with parameters that ensure denial

· Sufficient power throughout engagement

· Triggered EA

· Deliver tasked Effective Isotropic Radiated Power (EIRP) and have previously executed viable probe

· SEWOL must maintain no less than 90% effective denial of tasked EA signals

· Ability to abide by limitations

· SEWOL must abide by legal requirements by country 100% of the time

· SEWOL must know when and what RMTs can fire on specific targets

· SEWOL must abide by Commanders Deconfliction Assessment (CDA) constraints

· SEWOL must identify when it is unable to schedule a task and assign a reason for not scheduling the task against the proposed schedule

· Ability to dynamically task and re-task based on changes in environment

· SEWOL must allow an update to parameters for an executing task

· SEWOL must attempt 2 retries of a failed SEW task

· SEWOL must enable operators to re-engage individual signal EA tasks once failed within 5 minutes excluding RMT peaking time ES driven EA

· SEWOL will conduct ES and EA tasks on the true target data where “true target data” is the data ingested from Target Data template except for the following parameters SEWOL will measure and override for correlated SOIs:

· Uplink Center Frequency

· SEWOL must hold visibility and Signal to Noise Ratio (SNR) data, correlated to SOIs, to drive EA weapon-target-pairing ES Triggered EA

· An EA engagement can be configured to be triggered by ES data hits.

SEWOL must have an ability to view data via a Common Operating Picture (COP). The following are the COP requirements for MVP.

Common Operating Picture (COP)

· Ability to verify approved schedule is executing as tasked

· SEWOL must export a readable log of:

· what was tasked

· SOI data off RMT

· what specific SOI is up and down

· task start and end time

· antennae pointing info and times

· This data must be pulled and saved for the SEW tasks

· completed

· canceled

· failed

· This data is categorized by SEW Task Prior to executing SEW missions, SEWOL must be able to generate the mission plan (weapon / target pairing). The following are the mission generation requirements for MVP.

Mission Generation

· Ingest, review, upload, modify, and delete MTO and Target Data via formatted file structure (csv) for use in mission generation. Targets are defined as signals of interest, networks of interest (which consists of signals), users of interest (which consist of signals and/or networks of interest), and transponders.

· Prevent unauthorized actions by enforcing role-based access controls (RBAC)

· To effectively generate asset tasking, SEWOL requires Peaking information

· Target peaking Frequency

· Center Frequency

· Downlink Polarity

· Antenna Pointing data

· Satellite Two Line Elements (TLEs) pulled from the Unified Data Library (UDL)

· Manual TLE input by operator

· Manually point aperture using Azimuth, Elevation, and Polarity

· Transponder

· Transponder Name

· Frequency range and Bandwidth

· Transponder Translation Frequency

· Uplink/Downlink Frequency

· Uplink/Downlink Polarity

· Weapon Target pairing

· Needs to account for emplacement of RMT relative to transponder footprint/probe data and evaluate which RMT would be most effective

· Probes

· Probe is not required for ES but any ES taskings should reference non-stale probe data for target

· Probe required in advance of EA tasking and the probe result data for that transponder/beam need to be stored for future reference and application to other tasks on that target.

· Conduct Probes as separate mission like EA tasking Tasking

· For ES missions, SEWOL should automatically:

· Reference Peaking info

· Do Weapon / Target Pairing

· Use Probe data/footprint data

· Scope multiple ES taskings across multiple transponders in a single satellite to one RMT

· Determine and define scan parameters for assigned SOIs

· Min/max Frequencies range or Center frequency and bandwidth. (RMT does not handle specific frequencies/information in its scans well because it is looking for EXACT parameters)

· Modulation type

· Baud Rate

· SNR threshold/better

· Bandwidth

· ES task info reported in logs (RMT and SOI events)

· Provides live mission logs with mission relevant data that can be viewed post execution

· Exportable mission event logs both for individual tasks and collective tasks

· Antenna status events

· SOI Information:

· Time

· Center Frequency

· Modulation

· Baud Rate

· Bandwidth

· Downlink Polarity

· Signal to Noise Ratio For EA missions, SEWOL should Automatically:

· Reference Peaking Info

· Do Weapon Target pairing with probe data

· If no probe data/stale should probably probe

· Build EA tasks using RMT required parameters for the selected technique

· Clearly indicate Transmission status either live or inactive

· Mute/Unmute individual/all SDRs/RMT

· SDR and High-Power Amplifier (HPA) values need to be modifiable by operators during execution

· Most important fields:

· Uplink Center Frequency

· Modulation

· Baud

· Bandwidth

· SDR Gain

· HPA attenuation

· Task 2 EA tasks to one RMT (they must be on the same SAT)

· Both should have Interference to Signal Ratio (ISR) enabled unless there is a problem between uplink/downlink footprints. (May have more than one signal per task but it requires no ISR and manual monitoring at this time)

· ISR may not be required depending on the situation.

· Independently set ISR restrictions on power

· ISR needs to be able to manipulate the SDR’s attenuation and the HPA’s gain.

· Operators should be able to restrict the ISR’s function to manipulate either the SDR or the HPA, so that only one can be changed

· EA Task info Reported in logs

· Provides live mission logs with mission relevant data

· Exportable mission event logs both for individuals and collectives

· Info Required in logs

· Transmit State

· Power output of antenna

· Uplink Polarity

· Uplink Center Frequency

· SDR gain

· HPA Attenuation

· EIRP value

· Confirmation of ISR meeting desired level SEWOL must be able to update the mission plan under various conditions. For MVP, the following requirements are noted.

Automatic Re-tasking

· SEWOL must be able to accomplish all functions with minimal failures, ensuring rapid recovery through automated processes or by enabling manual operator interventions as outlined below:

· SEWOL must autonomously replan in response to RMT failures or communication losses, as indicated by a lack of response from the RMT.

· SEWOL must inform operators when and why either RMT or SEWOL experienced an error

· SEWOL will identify RMT status failures to the operator and allow the operator to manually establish a maintenance window which will temporarily block RMT for tasking and automatically trigger a replan Error Resolution

· SEWOL needs to recognize error messages from RMT and react to them.

· For example, when a known error occurs, SEWOL should execute steps such as:

· Cancel task

· Stop Service

· Wait ~2 mins

· Start Service

· Wait ~2 mins

· Re-task RMT

· Sometimes there are no error messages and the RMT gets into a bad state without triggering a notification. SEWOL needs to be able to recognize these patterns, respond, log and notify operators, accordingly when they occur.

· Example: Task is accepted and begins to peak but gets stuck at an unexpected AZ/EL

· SEWOL will cancel and restart Antenna pointing service before re-tasking

· Needs to allow operators to view error info and manually take troubleshooting actions when SEWOL fails to resolve the issue.

· LIVE Antenna status

· Shows current Antenna health and status

· Show current antenna activity: Peaking, tracking, moving, transmitting, idle, etc.

· Show current EIRP and pointing azimuth / elevation

UNCLASSIFIED

UNCLASSIFIED