SEWOL RFI - Final.docx

(U) SPACE ELECTROMAGNETIC WARFARE OPERATING LOCATION (SEWOL)

(U) REQUEST FOR INFORMATION (RFI)

(U) SOURCES SOUGHT

(U) 24 JULY 2025

(U) UNITED STATES SPACE FORCE (USSF)

(U) SPACE SYSTEMS COMMAND (SSC)

UNCLASSIFIED

(U) COMBAT SYSTEMS PROGRAM OFFICE

UNCLASSIFIED

1.0 (U) Purpose:

(U) This is a Sources Sought Notice. The Space Systems Command (SSC) located at Los Angeles Air Force Base, California, is seeking Statements of Capabilities (SOC) and demonstrations of software from interested parties to support the SSC, Combat Power Directorate, Electromagnetic Warfare System Delta, Combat Systems Branch (SSC/SZWC) requirement for the Space Electromagnetic Warfare Operating Location (SEWOL).

(U) The Government is conducting market research to inform its Acquisition Strategy and aims to identify potential sources that can meet the SSC/SZWC’s requirements. The Government reserves the right to set this acquisition, or portions thereof, aside for small business – to include socially and economically disadvantaged businesses, 8(a) firms, veteran-owned, or woman-owned businesses.

(U) The Government is seeking contractors interested in and capable of providing all technical, managerial, and logistical efforts required to rapidly design, develop, and deliver the SEWOL system.

2.0 (U) Background and Description:

(U) Description: This effort encompasses all technical, logistics, and software development required to design, develop, and deliver the SEWOL tactical command and control system. It includes but is not limited to: software architecture design and development, communications/networking design and development, integration of Government Furnished Equipment (GFE) Space Electromagnetic Warfare (SEW) weapon systems, sustainment, logistics program definition and execution, DevSecOps support and execution, and operator training program development and execution. The SEW weapon systems for integration with SEWOL include the Remote Modular Terminal (RMT) with other systems to follow, such as Bounty Hunter, Counter Communications System (CCS) Meadowlands, and additional future SEW systems.

(U) It is important to note that SEWOL's development is currently underway and reached its 2-year development milestone in May 2025. Depending on the contractor’s approach, existing software may be leveraged as GFE to expedite the delivery of the final system.

(U) Background:

(U) SEWOL System:

(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 of 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 EMSO warfighter capabilities with fewer resources, ensuring continuity of operations from distributed nodes.

(U) Five primary SEWOL capabilities are:

1. (U) Common SEW Data Repository: Serves as a source for SEW operational data relating to the systems operated within the SEWOL architecture.

2. (U) SEW Common Operating Picture (SEWCOP): Provides flexible and dynamic battlespace awareness through a visual, searchable, and interactive near real-time picture of current SEW activities. Displays relevant SEW information, such as targets, SEW tasking, SEW activities, network availability, and system status to tactical operators and operational level planners.

3. (U) Integration of SEW systems with a Common Operating Interface (COI): Provides a unified interface to efficiently command and control multiple types of SEW systems across various geographic regions, classifications, and network connections.

4. (U) Tactical Command and Control (Tac C2) Infrastructure: Integrates mission planning, execution, and C2 applications. Provides automated operations and specific tasking to SEW systems. Is capable of commanding and controlling multiple simultaneous systems with a variety of missions for combined effects. Functionality must include ingestion of higher-level operational tasking, weapon-target pairing, battlespace orchestration, automated and manual scheduling, automated execution tasking, dynamic re-tasking, and execution monitoring for a multitude of end units against numerous targets.

5. (U) Infrastructure for mission agility, scalability, resilience, and cybersecurity: Utilizes a DevSecOps environment which incorporates robust cybersecurity and allows timely, coordinated, and secured updates to software for vulnerability patching and capability addition. Software must include a modular design to ensure growth and integration with future systems. The SEWOL infrastructure will enable continuity of operations across all phases of conflict by using a redundant architecture and support a degraded ops capability.

(U) Remote Modular Terminal (RMT):

(U) The RMT is a ground-based SEW system engineered to be more compact and cost-effective, enabling deployment in large quantities. These smaller terminals are intended to complement larger SEW systems like the CCS Meadowlands. Operated remotely from SEWOL, the RMTs allow personnel to manage them from a secure location. The RMT system will be the first hardware platform integrated into the SEWOL network.

(U) Bounty Hunter:

(U) Bounty Hunter is a ground-based, deployable, tactical SEW system designed to provide SATCOM geolocation and interference detection capabilities by monitoring, detecting, characterizing, and geolocating both friendly and adversarial electromagnetic interference across multiple radio frequency bands to support Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance (C4ISR) missions. It enables operational commanders to locate sources of intentional or unintentional electromagnetic emissions, ensuring situational awareness for immediate threat recognition, targeting, planning, and the conduct of future operations.

(U) CCS Meadowlands:

(U) Meadowlands represents the next generation Counter Communications System (CCS) and is designed to replace the CCS 10.2. As a tactical electromagnetic warfare (EW) system, Meadowlands is engineered to detect, identify, and disrupt adversary communications systems. It forms as a key element of the U.S. military's electromagnetic warfare architecture. This advanced system is a lighter, more compact version of its predecessor, featuring enhanced remote capability, automation, transportability, a reduced footprint, and multi-system management. Leveraging an open architecture software system, Meadowlands simplifies software updates, enabling warfighters to stay ahead of evolving threats and missions.

3.0 (U) Government Reference Documents:

(U) The Government will provide the following reference documents alongside this RFI to provide context for the full requirement of the SEWOL effort (see Attachments):

1. (U) SEWOL Strategic Product Roadmap

a. Description: Provides context for the SEWOL lanes of effort and major capability releases expected

2. (U) SEWOL Program Definition

a. Description: Provides context for the contractor to understand the totality of the SEWOL program

3. (U) SEWOL Minimum Viable Product (MVP) Description

a. Description: Provides the set of capabilities which SEWOL must be capable of performing to meet the Minimum Viable Product for operations

4. (U) Capability Needs Statement (CNS) Excerpt

a. Description: Provides a user-generated description of the functionalities SEWOL must perform to execute the mission

4.0 (U) Statement of Capability (SOC) Submission Instructions:

(U) Responses must be received by the Government no later than 18 August 2025.

(U) SOC responses shall not exceed ten (10) pages total, any pages beyond the limit will not be considered. Responses shall be submitted in MS Word 2000 (or newer). Responses should be formatted to match the structure of the requested information as outlined below. Page size shall be 8.5 x 11 inches; single spaced with text no smaller than 10-point Times New Roman; font size within graphics and tables shall be no smaller than 8-point Times New Roman. Margins shall be one inch on all sides.

(U) Respondents shall provide a classified response to this RFI up to the TOP SECRET/SCI level. Submit all classified responses via an appropriate classified network (SGN addresses are provided below). Unclassified submissions will not be considered.

(U) Please submit responses via email to all the following points of contact:

(U) Contracting Officer: Jacqueline Ninonuevo

(U) Contracting Officer Email: jacqueline.ninonuevo@spaceforce.mil

(U) Contracting Officer Classified Email: jacqueline.ninonuevo@a1lan1.cal0.admin.af.cti.sgn

(U) Program Manager: Maj Dennis Sieber

(U) Program Manager Email: dennis.sieber.1@spaceforce.mil

(U) Program Manager POC Classified Email: clifford.r.rudder@a1lan1.cal0.admin.af.cti.sgn

(U) Firms providing confidential/proprietary information shall separately and clearly identify and mark all confidential/proprietary information. The USSF will take all necessary steps to protect/safeguard any confidential/proprietary information provided. The USSF will NOT be held responsible for any proprietary information not clearly marked. Please be advised that all submissions become Government property and will not be returned. All material provided in response to this notice shall be kept non-confidential and non-proprietary to the maximum extent practicable.

(U) SSC has entered into contracts with Federally Funded Research and Development Center (FFRDC) and/or Systems Engineering and Technical Assistance staff working for the Government. These could include, but are not limited to: The Aerospace Corporation, Tyto Corporation, SAIC, Blue Sky Innovators, RSE, ARK GSI, Mantech, Tecolote, Emolbi and LinQuest Corporation. These companies support the Government by performing technical reviews, systems engineering and integration analyses, cost estimation, and other advisory services. Respondents are hereby notified that all responses will be provided to SSC support contractors for services to SSC. These companies are bound by appropriate non-disclosure agreements with the USSF. If Respondents disagree to the release of its RFI response to any of the aforementioned firms, the Respondent must clearly state this restriction in the cover letter accompanying the RFI response.

5.0 (U) Statement of Capabilities Requested Information:

(U) Interested vendors must submit a Statement of Capability (SOC) in a narrative report to include all of the following information.

A. (U) Company Information B. (U) Corporate Capabilities & Experience C. (U) Answers to Technical Questions D. (U) Answers to Contractual/Business Questions

A. (U) Company Information:

1. (U) Company name

2. (U) Company’s ownership and other relevant information

3. (U) Personnel/Business size classification (Small/Large Business, HUB, veteran, etc.)

4. (U) Mailing address

5. (U) Point of Contact (POC) including e-mail and telephone numbers

B. (U) Corporate Capabilities & Experience:

(U) Describe previous work your company has performed and company expertise which is relevant to the role of a Prime Contractor. Also provide information related to:

1. (U) Experience developing, testing, and delivering a tactical C2 system.

2. (U) Experience integrating with regional C2 (operational C2) systems and external cloud-based databases and services.

3. (U) Experience developing or interfacing with operational SEW weapon systems.

4. (U) Experience with Agile software development supporting DoD software acquisition efforts, to include use of DevSecOps.

5. (U) Experience with test driven development and integrated test teaming.

6. (U) Experience iteratively delivering tested and operationally acceptable software versions in recurring increments.

7. (U) Experience porting and integrating existing code (GFE) into mission software baseline.

8. (U) Experience being the lead integrator on a system of systems, to include integration with legacy hardware and new side-by-side development programs.

9. (U) Corporate and teaming experience to develop, integrate with, and test operational components at this magnitude.

C. (U) Technical Questions:

1. (U) What software development processes and solutions would you use to execute this effort?

a. (U) Will the contractor modify an existing product or start from new?

2. (U) What security architecture would you use to execute this effort?

3. (U) How would you implement the software infrastructure to support SEWOL?

a. (U) What technical architecture would you propose?

b. (U) What processes would you use?

4. (U) How would you approach contractor and Government test, to include software, integrated software and hardware, automated testing, and regression testing?

5. (U) What do you see as the major challenges (technical, security, programmatic, etc.)?

6. (U) What Information or GFE will you need from the SEWOL program to ensure success? When will you need that information?

D. (U) Contractual / Business Questions:

1. (U) Do you have an estimated Period of Performance to complete the SEWOL requirement?

2. (U) Are you a small business? If not, what do you believe would be a good goal for Small Business set aside for this requirement?

3. (U) Do you plan to partner with other contractors? Is so, what are the expected capabilities or services you expect them to provide?

4. (U) Do you anticipate using any proprietary technology or information as part of the proposed solution?

5. (U) Discuss any key cost and schedule drivers, cost tradeoffs, schedule considerations, and assumptions.

6. (U) Do you have any recommendations and rationale for an incentive and contract structure?

7. (U) What requirements would you recommend including in a potential future solicitation for the SEWOL effort?

8. (U) In the context of an acquisition strategy that emphasizes speed to capability delivery and enhanced transition flexibility, please provide inputs and recommendations for CDRLs that enable the following:

a. (U) Fast development, cost savings, and successful contractor pivot or transition in the event of nonperformance or failure.

b. (U) Government’s right to use, modify, reproduce, and maintain continuity of the deliverables, especially during a transition to another contractor.

c. (U) Rapid feedback cycles for incremental delivery, continuous integration, and iterative reviews.

d. (U) Clear metrics that allow both contractor and government to monitor progress and quality effectively.

9. (U) Do you have any recommendations and rationale for using non-traditional contract mechanisms for this acquisition such as Commercial Solutions Opening or Other Transactions (OTs)?

6.0 (U) Technology Demonstration Administrative Requirements:

(U) The Government welcomes a demonstration of any software solution currently in development or in operations which is able to demonstrate the implementation of one or more SEWOL MVP functions. This may include, but is not limited to:

1. (U) User interfaces for tactical scheduling and execution monitoring.

2. (U) Automated task scheduling, execution and system orchestration of a large number of systems.

3. (U) Remote operations interface capabilities with an existing weapon system, with particular emphasis on Communications or EW systems.

(U) Should a vendor wish to demonstrate operational software to the Government, it should be clearly noted within the submission of the SOC. Additionally, all demonstrations must be held no later than 2 weeks following the suspense of this RFI. The Government makes no guarantees of the ability to travel to witness a demonstration, however, will make every attempt to facilitate a virtual demonstration on the appropriate system.

(U) A technology demonstration is not required for this RFI, and lack of current software does not preclude an interested vendor from submitting a SOC.

7.0 (U) Disclaimers and Notes – THIS IS A REQUEST FOR INFORMATION ONLY. This notice is issued solely for information and planning purposes. It does not constitute a solicitation (Request for Proposal or Request for Quotations) or a promise to issue a solicitation in the future. This notice does not commit the USSF to contract for any supply or service whatsoever. Furthermore, the USSF is not currently seeking proposals. Responders are advised that the USSF will not pay for any information or administrative costs incurred in response to this notice. The Government will not assume liability for costs incurred by any attendee for travel expenses or marketing efforts. All costs associated with responding to this notice will be solely at the responding party's expense.

(U) Attachments:

1. (U) SEWOL Strategic Product Roadmap

2. (U) SEWOL Program Definition

3. (U) SEWOL Minimum Viable Product (MVP) Description

4. (U) Capability Needs Statement (CNS) Excerpt image1.png