RFI FA8723-22-R-0008 MWTP.pdf

REQUEST FOR INFORMATION

FA8723-22-R-0008

SSC/ECQ Missile Warning Threat Planning

1.0 Description

1.1 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 from an interested contractor whom can create and generate files for the Scenario Injection Generator System (SIGS) from a separate system.

1.2 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 Space Force is not at this time seeking proposals and will not accept unsolicited proposals. Those responding are advised that the 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 North American Aerospace Defense Command (NORAD) Cheyenne Mountain Complex- Integrated Tactical Warning/Attack Assessment (NCMC-ITW/AA) and Legacy Space systems provides timely, accurate, 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/NORTHCOM, USSTRATCOM, and US Space Force command with the information management, decision aids, and connectivity required to monitor, assess, plan, and execute assigned strategic and theater missile warning, space operations, and missile defense missions. The Combatant Commanders Integrated Command and Control System (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 for the Integrated Tactical Warning/Attack Assessment (ITW/AA) community 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. Emerging threats require new and innovative Strategic C2 approaches for strategic warning time analysis, attack origination identification, weapon system identification, multi-phenomenology track custody, event correlation, threat determination, and multi-domain attack characterization. Legacy Space C2 systems include SPADOC (Space Defense Operations Center)/SPEAR (SPADOC Emulation Analysis Risk Reduction) and a front-end communications system the Communications Processing Subsystem (CPS).

3.0 Problem Set

ECQN/Z requires an updated dynamic, flexible scenario development system to generate scenario files for injection into CCIC2S mission and Legacy Space communications systems or applications for training, exercise, and testing purposes. The system must support changing and evolving missions and provide the ability to create new scenarios, or modify existing scenarios rapidly, to enhance training by preventing operators from memorizing scenarios and anticipating repetitive outcomes. This will provide a testing capability that reacts quickly and effectively to new threats, requirements, and dynamic inputs. Scenarios may assist in testing corner cases and troubleshooting software development issues, ensuring our ability to meet requirements even as we modify the systems. In addition, the system must provide the capability to generate realistic scenarios involving emerging threats. Additionally, the contractor shall be able to demonstrate the ability to deliver the requirements outlined below NLT 30 days after contract award.

3.1 Delivery Period: Expected Period of Performance - One Year.

3.2 Limitations:

3.2.1 The contractor will be reporting to the System Program Office (SPO).

3.3 Security Requirements: The Contracting team is required to have a SECRET clearance at the time of acceptance of responsibility. Relevant DoD Approved DoDD 8140 (previously 8570.01M) Baseline Certifications as well as a Computing Environment (CE) certification, based on the equipment and software to be worked with for primary duties, are required.

4.0 Requested Information

The Government is seeking to identify potential vendors who have experience in in developing dynamic scenario generation capability to achieve the objectives outlined below:

4.1 Develop a government approved technical solution for implementation of a dynamic, flexible scenario development system to generate scenario files for injection into CCIC2S mission applications for training, exercise, and testing purposes.

4.2 The technical solution shall provide Scenario Injection Generator System (SIGS) compatible scenarios for space messages in the MODE I and ADCCP formats.

4.2.1 The inputs will be Collateral, Contributing, Dedicated and Other Sensors.

4.3 Technical solution will be required to function across multiple systems and subsystems of the CCIC2S and Legacy Space C2 networks.

4.4 Examples of previous solutions that provide SIGS compatible scenarios for Air

Messages.

4.5 Technical solutions that apply the Space Catalog DTG and range to the SIGS compatible scenarios.

4.6 Technical solution that will require on-site Help Desk support.

4.7 Demonstrate examples where feedback from End User was incorporated into existing applications.

4.8 Demonstrate examples using .TBL files, Common Message Format (CMF) messages, Tab37 messages, Air messages, Space messages, and Global Summary Messages (GSM).

4.9 Demonstrate examples with generating highly accurate and realistic scenarios for

USSTRATCOM, the JCS, and other COCOM users for National-level exercises.

4.10 Solution examples that provide a Subject Matter Expert (SME) for the Missile Warning

Training Suite component of the JIMDTS effort led by STRATCOM to create a toolkit of applications for use in training and exercises related to Missile Warning and Defense.

4.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.

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

5.0 Responses

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

5.2 White papers are due no later than 25 February 2022, 1600 MST. Responses shall be limited ten pages relative to paragraph four above and submitted via e-mail to Mr. Corey Chopko at corey.chopko@spaceforce.mil, Capt Jexenia Bennett at jexenia.bennett.1@spaceforce.mil, Mr. Ben Shelley at benjamin.shelley.1@spaceforce.mil, and Ms. Ashley Esquivel at ashley.esquivel@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

5.3 The white paper shall provide administrative information, and shall include the following as a minimum:

5.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.

5.3.2 Recommended contracting strategy.

5.3.3 Recommended staffing plan.

5.3.4 Recommended Level of Effort (LoE) estimated total hours to complete project.

5.3.5 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 51990, All Other Professional, Scientific, and Technical 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 35 million dollars in annual receipts. Respondents 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.

5.3.6 The facility security clearance of the respondent.

The number of pages in the administrative section of the white paper shall not be included in the 10-page limitation. The 10-page limitation applies only to the technical portion of the white paper.

6.0 Industry Discussions

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

7.0 Questions

Questions regarding this announcement shall be submitted in writing by e-mail to Mr. Corey Chopko at corey.chopko@spaceforce.mil, Capt Jexenia Bennett at jexenia.bennett.1@spaceforce.mil, Mr. Ben Shelley at benjamin.shelley.1@spaceforce.mil, and Ms. Ashley Esquivel at ashley.esquivel@spaceforce.mil, by 22 February 2022, 1600 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 22 February 2022, 1600 MST will be answered.

8.0 Summary

THIS IS A REQUEST FOR INFORMATION (RFI) ONLY to identify sources that can establish a MFA solution. The information provided in the RFI is subject to change and is not binding on the Government. The Space Force 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.