IDSS RFI Final Version 25Oct2025.pdf

SZQN RFI-IDSS Page 1 of 6

REQUEST FOR INFORMATION

Subject: Integrated Database System Support (IDSS)

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 on how to sustain and enhance the Integrated Database System Support (IDSS) system, which is a web-based application residing on the North American Aerospace Defense Command (NORAD/NORTHCOM) Non-Classified Internet Protocol Router Network (NIPRNet) and the Secret Internet Protocol Router Network (SIPRNet). IDSS is an incident report life cycle management system which is actively used by the ITW/AA community, to include NORAD, USNORTHCOM, United States Space Force (USSF), and associated Government Program Office contractors’ Government’s primary goals are the continue sustainment of the system, while also modernizing the hardware and the software technical baselines.

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 the 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. Any literature received from this will aid the Space Force in identifying potential 8(a) firms.

2.0 Background

IDSS is a web-based application (.NET and SQL) used by over 150 users for data tracking and data management purposes. The system consists of three major components: the Integrated Incident Report (IR), Standard Change Form (SCF), and Integrated Weapon System Database (IWSD). Currently, IDSS is deployed and maintained at the Cheyenne Mountain Space Force Station (CMSFS). The system is configured behind a screened subnet (Demilitarized Zone), where there is currently no way for user notifications in to or out of the applications. The below figure illustrates the basic configuration of IDSS.

SZQN RFI-IDSS Page 2 of 6

The Incident Report (IR) application tracks incident reports and System Center Outage Reports (SCOR) and serves as a database repository for meeting minutes related to these events.

Additionally, the subsystem allows users to document unexpected behavior on operationally accepted mission systems and systems under test.

The Standard Change Form (SCF management subsystem allows users to create SCFs, system user procedures, and System Change Requests (SCR). The SCFs and SCRs database repository is used to store requested system changes, address deficiencies in the system and technical documentation, and to modify mission configurations without requiring a new software build.

The Integrated Weapon System Database (IWSD) subsystem is a database repository that provides version control of programs, systems, interfaces, and messages. It provides information to engineers who are developing new systems to interact with current systems and require their message interpretation or interface connections to be consistent across mission systems.

The IDSS system includes cybersecurity reporting features specific for the CMSFS Network Operations Center (NOC) subsystem. It is used by system administrators to create and manage cybersecurity incidents. A repository stores these reports for electronic retrieve and review.

Both IDSS unclassified and classified systems have active Risk Management Framework (RMF) Authority to Operate (ATO): U-IDSS ATO approved December 2023 and C-IDSS approved February 2024.

SZQN RFI-IDSS Page 3 of 6

3.0 Requested Information

The Government is seeking to identify potential 8(a) firms who have experience with configuration and data management systems accessible through NIPRNet and SIPRNet. 8(a) firms must also have experience with obtaining and sustaining a Risk Management Framework (RMF) Authority to Operate (ATO). Experience with conducting technology refreshes and cloud-migrations is preferred.

3.1 Objective 1: Sustainment

Conduct IDSS sustainment, operations, cybersecurity, and software maintenance releases for the IDSS equipment located in Cheyenne Mountain Space Force Station (CMSFS) in Colorado Springs. IDSS consists of NIPRNet and SIPRNet servers with the following applications: 1) Integrated Incident Report (IR) Database, 2) Standard Change Form (SCF) Database, 3) Integrated Weapon System Database (IWSD) Database, and 4) NOC System. The current cybersecurity ATO for IDSS must be maintained and renewed, to include following the processes, procedures, and production of documentation necessary for any system updates.

3.2 Objective 2: Technology Refresh/Modernization

1. IDSS was first delivered in 2012 and refreshed in 2017. Since then, IDSS has been maintained as a sustainment program. The Government requires either a Hardware/Software (HW/SW) technology refresh of the existing system OR a SW refresh with a migration of the existing system to a cloud environment.

2. Most IDSS hardware and software requires a technology refresh. This includes hardware such as hard drives, laptops, and servers as well as software such as licenses for virtual machines, databases (SQL), browsers, and application development (.NET). A migration plan, with risks and contingencies identified, will be required to support the migration of all databases, server code, and data to a technology refreshed environment. All supporting cybersecurity documentation must be updated and submitted to maintain the active ATOs. The migration process, hardware and software refresh, including planning, testing, executing, and documentation, should be completed in 12 months or less.

3. A cloud migration should include all IDSS databases, server code, and data to include the existing operational, test, and development environments. IDSS unclassified must be accessible through NIPRNet and IDSS classified must be accessible through SIPRNet.

Data associated with these systems must align to DoD Cloud Computing Security Requirements Information Impact Levels (IL) 5 and 6. The cloud environment must provide services to enhance the existing cybersecurity posture and support automation of security audits. The environment must allow scalability based on demand, enabling IDSS to handle sudden spikes in traffic or accommodate growth in number of users.

Redundancy and reliability of the cloud environment should minimize the risk of downtime and ensure high availability for applications. There are existing government approved cloud environments that should be considered for this effort such as Cloud One and Platform One, but not limited to any of these solutions/environments. A migration plan must include the ability to maintain and/or secure active ATOs for the systems on the cloud platform.

SZQN RFI-IDSS Page 4 of 6

3.3 Objective 3: Enhancements

This objective encompasses any improvements to the current system to improve usability, modernizing the look, adding new features, increasing efficiencies with system management, improving the cybersecurity posture, and/or leveraging compatibility with modern software and devices. They may include, but are not limited to:

• Update the graphical user interface (GUI) of the .NET application with current design trends to meet modern standards and user expectations. Leverage design tools, UI libraries, prototyping tools, automated testing tools, and packaging tools.

• Create the ability for the applications to send users notifications via e-mail for alerting to when a request, action or incident has been submitted, changed, or reached a milestone.

• Create the ability for users to login using Multi-Factor Authentication (MFA).

• Replace IDSS with a customizable COTS application that meets all required functionality. Ensure ability to migrate, control, and retain data. The system must offer improvements in cost, system administration, cybersecurity, and ease of management.

4.0 Responses

4.1 Interested parties 8(a) firms are requested to respond to this RFI with a white paper.

4.2 White papers are due no later than 8 November 2024, 1400 Mountain Time. Responses shall be limited to 10 pages for Section 2 and submitted via e-mail to Heather Baldwin at heather.baldwin.4@spaceforce.mil, Lt. Makayla Hansen at makayla.hansen.2@spaceforce.mil and Matthew Sheridan at matthew.sheridan.5@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. Any CUI information must be submitted via DOD SAFE.GOV to heather.baldwin.4@spaceforce.mil, makayla.hansen.2@spaceforce.mil and matthew.sheridan.5@spaceforce.mil.

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. Recommend staffing plan/ skillsets to complete the proposed effort.

4.3.4. Recommend Level of Effort (LOE) estimated total hours to complete the project.

4.3.5. Respondent must attest to SBA’s 8(a) eligibility with responses to the criterial below.

SBA’s 8(a) Program Status:

mailto:heather.baldwin.4@spaceforce.mil mailto:makayla.hansen.2@spaceforce.mil mailto:matthew.sheridan.5@spaceforce.mil mailto:heather.baldwin.4@spaceforce.mil mailto:makayla.hansen.2@spaceforce.mil

SZQN RFI-IDSS Page 5 of 6

Eligibility. The CO can verify a firm’s 8(a) status by checking SBA Dynamic Small Business Search and reviewing the company 8(a) Entrance and Exit Dates.

To qualify for the 8(a) program, your business must:

• Be a small business according to SBA Size Standards Small Business Size Standards

(sba.gov)

• Not have previously participated in the 8(a) program

• Be at least 51% owned and controlled by U.S. citizens who are socially and economically disadvantaged

• Have a personal net worth of $850 thousand or less, adjusted gross income of $400 thousand or less, and assets totaling $6.5 million or less

• Demonstrate good character

• Demonstrate the potential for success such as having been in business for two years

a) Business type the Government is seeking responses from 8(a) firms for the IDSS requirement based upon North American Industry Classification System (NAICS) code 518210, Data Processing, Hosting, and Related Services. Please provide your 8a status in SAM.Gov for this NAICS code.

b) Please provide what existing contract vehicles your firm is eligible to receive an award as an 8(a) Participant under. Some examples are GSA OASIS+ MAC IDIQ 8(a) Pool and 8(a) STARTS III GWAC.

4.3.5 The facility security clearance of the respondent/ 8(a) firm.

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 8(a) firms. 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 Heather Baldwin at heather.baldwin.4@spaceforce.mil and makayla.hansen.2@spaceforce.mil by 31 October 1400 Mountain Time. 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 31 October 1400 Mountain Time, 1400 MT will be answered.

mailto:heather.baldwin.4@spaceforce.mil mailto:makayla.hansen.2@spaceforce.mil

SZQN RFI-IDSS Page 6 of 6

7.0 Summary

THIS IS A REQUEST FOR INFORMATION (RFI) ONLY to identify sources that can sustain and enhance the Integrated Database System Support (IDSS).

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.