SysOps Sources Sought_19 May 2025.docx

THIS IS A SOURCES SOUGHT ANNOUNCEMENT ONLY.

SOLICITATION NUMBER - FA8723-25-R-0006

This sources sought announcement is not to be construed as a commitment by the Space Force to issue a solicitation or ultimately award a contract. Neither unsolicited proposals nor any other kinds of offers will be considered in response to this sources sought. No contract will be awarded pursuant to this announcement.

SOURCES SOUGHT

For North American Defense Command Cheyenne Mountain Complex – Integrated Tactical Warning/Attack Assessment (NCMC – ITW/AA) System Operations (SysOps) Trainer

14 May 2025 Space Systems Command (SSC) Battlespace Awareness Acquisition Delta (SZBN)

DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only Critical Technology Information, 31 October 2023. Other requests shall be referred to SSC/SZBN.

POC: Mr. Jeffery Burnside, 719-554-6486 DESTRUCTION NOTICE: Destroy by any method that prevents disclosure of contents or reconstruction of the document.

SysOps Trainer Sources Sought Announcement

SysOps Trainer SOURCES SOUGHT

SOLICITATION NUMBER - FA8723-25-R-0006

Introduction:

SYNOPSIS:

In accordance with FAR Part 10, Market Research, the United States Space Force (USSF), Space Systems Command (SSC), Battlespace Awareness Acquisition Delta (SZBN), Peterson Space Force Base (PSFB), CO is conducting market research to identify contractors that possess the capabilities to meet the anticipated requirements for the SysOps Trainer, specifically in the topic areas covered within this sources sought announcement. Please see the DRAFT Performance Work Statement (PWS) found in Attachment 1, DRAFT SysOps Trainer PWS for more details. The anticipated Period of Performance (PoP) for this effort is 15 months.

The Government may use responses to this Sources Sought for information and planning purposes. The technical specifications contained within this announcement and its attachments describe only the currently contemplated possible specifications and may vary from the actual specifications identified in any final documents.

This Sources Sought is only for the purpose of identifying potential sources as a part of market research. This is NOT a Request for Proposal (RFP) or Request for Quote (RFQ). Responses to this Sources Sought will not be considered as formal proposals/quotes and the Government does not anticipate making an award based on the responses to this Sources Sought. There is NOT an anticipated RFP/RFQ date at this time and funds are NOT presently available. Interested parties are encouraged to monitor all postings.

BACKGROUND:

The NCMC-ITW/AA Systems Program Office systems provide timely, unambiguous, and continuous warning and attack assessment of air, missile and space threats to North America, and geographical theaters. This system integrates and correlates missile launch and air surveillance information from certified sources to assess the nature of an enemy launch/attack and issues warnings to the US National Command Authority, Canadian National Leadership, National Military Command Center, and war-fighting Combatant Commanders. NCMC-ITW/AA and Legacy Space C2 systems provide NORAD and NORTHCOM, USSTRATCOM, USSPACECOM, and US Space Force command structures with the information management, decision aids, and connectivity required to monitor, assess, plan, and execute assigned strategic, space operations, and missile defense missions.

The CCIC2S is a unique, integrated, C2 “system of systems,” to provide data communication between external sensors and end users, mission processing for air and missile warning mission and system operations functions. The system supports national strategic objectives with ITW/AA and provides missile and air warning information to theater combatant commanders. The system consists of terrestrial and space-based sensor outputs, C2 nodes, and communication and dissemination links, connecting the US and Canadian defense information networks.

The System Center (SC) uses System Operations Application (SysOps) to monitor CCIC2S ITW/AA communications and applications. SC uses the live ITW/AA system for training and certification. SZBN Program Office has been tasked to create a SysOps Trainer. The intent is to train staff with an emulated SysOps.

SYSOPs TRAINER REquirements:

The Contractor shall design a SysOps training system identical to the existing operational environment for SysOps and the mission for System Center (SC) to perform training. The objective of the SysOps Trainer is to emulate the behavior, performance, and user interface of the operational SysOps to the greatest extent possible. Reference Attachment 1 for the Draft PWS that highlights the anticipated requirements.

Sources soughT instructions:

All information contained in this Sources Sought Announcement is preliminary, subject to modification, and is in no way binding to the Government. The Government will not pay for any information submitted in response to this request. The information requested will be used solely within the SSC/SZBN Program Office, along with the Program Office’s Advisory and Assistant Support (A&AS) contractors to facilitate decision making. No information will be disclosed outside of the Government.

The anticipated NAICS Code is 541512; the corresponding Small Business size standard is $34M. If the NAICS Code or Small Business size standard appears to be incorrect, please suggest an alternative NAICS Code and Small Business size for consideration.

Information Sought:

Interested parties should submit information as to the capabilities, capacity, and experience to perform the anticipated requirements set forth in the DRAFT PWS. Respondents are asked to provide their responses in the sequence the information is asked for.

Contractor Department of Defense Experience:

Describe your relevant experience (within 5 years) on contracts and requirements similar to those outlined below. Include the contract short name, numbers, brief description, PoP, and the agency/organization it supported.

a) International Traffic in Arms Regulations (ITAR) and security requirements up to the Secret level

b) Hire and retain uniquely skilled and experienced personnel

c) Provide Secret-cleared personnel and SIPR access requirements on day 1 of performance

d) Provide onsite CONUS services in a Secret environment

e) Department of Defense or Department of Air Force / Space Force Cyber Security compliance (i.e. Vulnerability Management, Cybersecurity Hardening, Security Monitoring and Incident Response, Multi-Factor Authentication, Compliance and Reporting) Relevant Experience in Software Development and Prototyping Environment:

Describe your relevant experience (within 5 years) on contracts and requirements similar to those outlined below. Include the contract short name, numbers, brief description, PoP, and the agency/organization it supported. Experience with:

a) Broadcom VMWare / ESXi development & integration with DoD weapon's systems

b) Operations Bridge Manager (OBM) User Interface (UI) and integration

c) Development Security Operations (DevSecOps) stature and Risk Management Framework (RMF) as the focus

d) Virtual platform (VLAN) integration

e) Virtual machine / cloud-based or hosted environment

f) Developing Department of Defense technical solutions for trainers that emulate behavior, performance, and user interface of existing systems

Relevant Experience on Similar System(s):

Describe your relevant experience (within 5 years) on contracts and requirements similar to those outlined below. Include the contract short name, numbers, brief description, PoP, and the agency/organization it supported.

a) Experience with the missile warning systems

b) Experience with the CCIC2S code baseline

Summarize your relevant experience (within 5 years), capabilities (skills, processes, tools, etc.), and risks to perform the objectives and achieve the desired outcomes within section X.

Business Information:

a) Company name and address;

b) Point of Contract;

c) Phone Number;

d) E-mail Address;

e) CAGE Code;

f) DUNS Number;

g) Business Size and Type of Small Business (if applicable);

h) Indicate all applicable NAICS which your company currently performs;

i) Facility security clearance

j) Specify if you are a U.S. or foreign-owned firm

k) Is your company on any existing multiple award IDIQs or other vehicles SSC/SZBN would be able to utilize for this effort? If yes, please include the contract number, PoP, contract ceiling, and the Government Contracting Officer contact information;

l) What do you perceive as barriers to competition?

m) Provide suggested contract types (i.e. firm-fixed price, cost-plus fixed fee, cost- reimbursement, etc.) best suited for these services.

n) Provide suggested contract line-item number (CLIN) arrangements best suited for these services.

Submission Details:

Interested parties that believe they have the above capabilities to perform as the contractor for this effort should submit no more than a 15- page response, addressing paragraphs 3.1.1 – 3.1.3, (cover page not included). Responses shall be submitted via a PDF or MS Word Document, with standard margins and a font size no smaller than 11 point. Responses shall be submitted to the Contracting Officer, Ms. Sydney Dugal at sydney.dugal@spaceforce.mil.

Responses are due no later than 03 June 2025, 12:00 pm (noon) Mountain Time. Responses received after this date and time may not be reviewed.

Questions regarding this announcement shall be submitted in writing by email to the Contracting POC stated above. Questions are to be submitted NLT 26 May 2025, 12:00 pm (noon) Mountain Time. Verbal, phone or fax questions will NOT be accepted. Questions shall NOT contain proprietary or classified information.

Please note, no phone calls or faxes will be accepted. Classified information will not be accepted. The Government will not award a contract solely based on this Sources Sought, nor will it reimburse the contractor for any costs associated with preparing or submitting a response to this notice. Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information. All information received that is marked Proprietary will be handled accordingly. Please be advised that all submissions become Government property and will not be returned. All Government and contractor personnel reviewing sources sought responses understand their responsibility for proper use and protection from unauthorized disclosure of proprietary information as described in 41 USC 423. The Government shall not be held liable for any damages incurred if proprietary information is not properly identified.

SysOps SOURCES SOUGHT

SOLICITATION NUMBER - FA8723-25-R-0006

image1.png