Scenario Creation and Injection Tool RFI 21 November 2023.docx

REQUEST FOR INFORMATION

Subject: SSC/SZQN Scenario Creation and Injection Tool

FA8723-24-R-0002

1.0 Description

The Space Systems Command (SSC) in support of the North American Aerospace Defense Command (NORAD) Cheyenne Mountain Complex-Integrated Tactical Warning/Attack Assessment (NCMC-ITW/AA) Program Office is seeking information to enhance Combatant Commanders Integrated Command and Control System (CCIC2S) and Legacy Space Systems with a scenario generation and injection tool. Recommendations are solicited. The tool will be used in two enclaves: CCIC2S and Legacy Space.

THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is issued solely for information and planning purposes – it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This request for information does not commit the Government to contract for any supply or service whatsoever. Further, the Government is not at this time seeking proposals and will not accept unsolicited proposals. Responders are advised that the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested party’s expense. Not responding to this RFI does not preclude participation in any future RFP, if any is issued.

2.0 Background

The NCMC-ITW/AA system provides 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 surveillance information from certified sources to assesses the nature of an enemy launch/attack and issues warnings to the US National Command Authority, Canadian National Leadership, National Military Command Center (NMCC) and war-fighting Combatant Commanders (CCMD). NCMC-ITW/AA and Legacy Space C2 systems provided NORAD/NORTHCOM, USSTRATCOM, 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.

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 nation strategic objectives with Integrated Tactical Warning/Attack Assessment (ITW/AA) and provides missile and air warning cueing, and engagement 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 Government requires a tool for creating and injecting scenarios in the test system that is virtualized, can handle multiple future message types, is expandable and can add additional injection capability with ease. This system is to replace the legacy Scenario Injection System (SIS) and various separate tools will be integrated into on suite of tools using modern coding techniques (containers).

3.0 Requested Information

The Government seeks to identify potential vendors who have experience with test tools and suites of tools that meet the following Objectives:

3.1 Develop a government approved technical solution for implementation of a scenario creation and injection tool to generate event-based scenario files and inject into CCIC2S mission applications for training, exercise, and testing purposes.

3.2 The technical solution shall provide scenario and injection capability for current CCIC2S producers and consumers as well a scalable solution to easily add future producers, consumers, and messages.

3.3 The technical solution will be required to function across multiple systems and subsystems of the CCIC2S, Air, and Legacy Space C2 networks.

3.4 Technical solution that can replace/update current SIS architecture with modern solution that will meet current and future training, exercise, and testing activities supported by subsystems within SIS.

3.5 Examples of Administrative and Production lead times for any hardware required, if any.

3.6 Integrating multiple software applications under one suite

3.7 Cyber Artifact requirements, Hardware/Software lists and version control

3.8 Vendor experience.

3.9 Ensuring Department of Defense and Department of Air Force Cyber Security compliance

3.10 Reasonable cost that includes a Rough Order of Magnitude for all costs expected for their testing tool (e.g., initial costs, licenses, reoccurring fees, support fees, and how much if any will a unclassified network internet connected and an air-gapped classified network)

3.11 Solution examples in assisting with the creation and review of USAF OT&E test documentation in accordance with AFOTEC standards to support formal testing of the ATM Missile Warning Training Suite which support operational training and evaluation of CCIC2S personnel.

3.12 Examples of Administrative and Production lead times for any hardware required, if any.

3.13 Integrating multiple software applications under one suite

3.14 Cyber Artifact requirements, Hardware/Software lists and version control

3.15 Ensuring Department of Defense and Department of Air Force Cyber Security compliance

3.16 Reasonable cost that includes a Rough Order of Magnitude for all costs expected for their testing tool (e.g., initial costs, licenses, reoccurring fees, support fees, and how much if any will a unclassified network internet connected and an air-gapped classified network)

3.17 Vendor experience.

3.18 Any Vendor recommendations for solutions.

4.0 Responses

4.1 Interested parties are requested to respond to this RFI with a white paper.

4.2 White papers are due no later than 19 Jan 2024, 1400 MST. Responses shall be limited to 10 pages for Section 3 and submitted via e-mail to Sydney West at sydney.west@spaceforce.mil, Mr. Kevin Thomas at kevin.thomas.60@spaceforce.mil, and Tracy McCorkle at tracy.mccorkle.ctr@spaceforce.mil. Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information. Please be advised that all submissions become Government property and will not be returned.

4.3 Section 1 of the white paper shall provide administrative information, and shall include the following as a minimum:

4.3.1 Name, mailing address, overnight delivery address (if different from mailing address), phone number, fax number, and e-mail of designated point of contact.

4.3.2 Recommended contracting strategy.

4.3.3 Recommended roll-out strategy.

4.3.4 Business type (large business, small business, small, disadvantaged business, 8(a)-certified small, disadvantaged business, HUBZone small business, woman-owned small business, very small business, veteran-owned small business, service-disabled veteran-owned small business) based upon North American Industry Classification System (NAICS) code 518210, Data Processing, Hosting, and Related Services. “Small business concern” means a concern, including its affiliates that is independently owned and operated, not dominant in the field of operation in which it is bidding on Government contracts, and qualified as a small business under the criteria and size standards in 13 CFR part 121. A small business concern for the purposes of this procurement is generally defined as a business, including its affiliates, averaging no more than 40 million dollars in annual receipts. Responders are cautioned, however, that this is a general description only. Additional standards and conditions apply. Please refer to Federal Acquisition Regulation FAR 19 for additional detailed information on Small Business Size Standards. The FAR is available at https://www.acquisition.gov/browse/index/far.

4.3.5 The facility security clearance of the Offeror.

The number of pages in Section 1 of the white paper shall not be included in the 10-page limitation, i.e., the 10-page limitation applies only to Section 2 of the white paper.

4.4 Section 2 of the white paper shall answer the issues addressed in Section 3 of this RFI and shall be limited to 10 pages.

5.0 Industry Discussions

SSC/SZQN representatives may or may not choose to meet with potential Offerors. Such discussions would only be intended to get further clarification of potential capability to meet the requirements, especially any development and certification risks.

6.0 Questions

Questions regarding this announcement shall be submitted in writing via e-mail to Sydney West at sydney.west@spaceforce.mil by 15 January 2024, 1400 MST. Verbal questions will NOT be accepted. Questions will be answered by posting answers in response to this RFI; accordingly, questions shall NOT contain proprietary or classified information. The Government does not guarantee that questions received after 15 January 2024, 1400 MST will be answered.

7.0 Summary

THIS IS A REQUEST FOR INFORMATION (RFI) ONLY to identify potential vendors who have experience with Scenario Creation and Injection Tools that can provide the best value to SZQN’s mission.

The information provided in the RFI is subject to change and is not binding on the Government. The Government has not made a commitment to procure any of the items discussed, and release of this RFI should not be construed as such a commitment or as authorization to incur cost for which reimbursement would be required or sought. All submissions become Government property and will not be returned.

SZQN RFI - Scenario Creation and Injection Tool Page 2 of 5