ISN-M RFI Cover Page_Final_9Apr26.pdf

Request for Information (RFI) For

Installation Service Node Modernization (ISN-M)

9 APR 2026

Prepared by:

Data Transport Branch (AFLCMC/HNIB)

Enterprise IT & Cyber Infrastructure Division (AFLCMC/HNI) Air Force Life Cycle Management Center (AFLCMC)

Hanscom Air Force Base (AFB), MA

Introduction and Purpose Bottom Line Up Front The United States Air Force (USAF) is issuing this Request for Information (RFI) to conduct market research and gather information on industry best practices and innovative solutions for a significant Information Technology (IT) initiative. The primary objective of this initiative is to bring our two disparate, physically and functionally separate network infrastructures into architectural parity by developing a single, modern technical framework to be applied across both.

The goal of this project is to optimize performance, enhance security, improve reliability and achieve significant operational efficiencies and cost savings. We are seeking to understand the capabilities, approaches, and experience of qualified vendors in planning and executing complex network consolidation projects of this nature.

This RFI is for informational and planning purposes only and does not constitute a solicitation for a formal proposal (RFP) or a commitment to issue one in the future. The information gathered from this RFI will be used to refine our requirements, inform our strategy, and identify potential partners who possess the expertise to meet our project goals. Responses to this RFI will not result in a contract award.

We appreciate your time and expertise in responding to this request and look forward to learning more about the solutions your organization can provide.

Background The USAF currently operates and sustains two physically and functionally separate mission critical infrastructures that provide network services to its installations [Non-Classified Internet Protocol Router (NIPR) and Secret Internet Protocol Router (SIPR) Installation Service Nodes (ISN)]. These services are provisioned through corresponding Installation Service Nodes (ISNs), which are datacenters that provide enterprise services at the site level, for each network. While both serve the USAF enterprise, they are in vastly different states of maturity and standardization, presenting a series of operational and strategic challenges.

Current State of the Infrastructures NIPR Infrastructure:

The NIPR ISN is a mature and stable system that is considered largely optimized for its mission.

However, a lengthy fielding timeline has created several system architecture differences to ensure each fielded system remains sustainable for at least 7 years. This lack of a consistent technical foundation presents challenges to standardizing enterprise-wide updates, streamlining system management, and optimizing sustainment efforts.

SIPR Infrastructure:

The SIPR ISN infrastructure has recently undergone a significant architectural evolution, transitioning from a decentralized, enclave-based system to a centrally managed enterprise service. This transition also prompted a change in the support model, moving from a purely Government-Owned, Contractor-Operated (GOCO) framework to a hybrid model that now includes Government-Owned, Government-Operated (GOGO) responsibilities alongside contractor support. The transition revealed that the lack of standardized technical architecture resulted in inconsistencies in how ISN stacks are installed, configured, and maintained across the enterprise.

This divergence across both NIPR and SIPR introduces unnecessary complexity and operational overhead, complicating enterprise-wide updates, system management, and sustainment efforts.

Any future solution must be implemented in conjunction with the current Department of the Air Force (DAF) Next-Generation Gateway (NGG)/Zero-Trust (ZT) implementation to address these challenges for both infrastructures.

The Core Challenge: Divergence and Inconsistency The recent SIPR transition brought to light a critical issue: NIPR and SIPR networks lack a common technical foundation. This has resulted in significant inconsistencies in how the equipment stacks are installed, configured, managed, and maintained across the enterprise. The future architecture will consolidate these into a centralized location at each installation. Known as an Installation Service Node/Installation Processing Node (ISN/IPN), this centralized location will offer a shared computing and storage infrastructure to host core services as well as some approved mission and functional applications.

The primary challenges stemming from this divergence include:

1. Increased Operational Overhead: Managing two different baselines requires separate training, documentation, and sustainment procedures, increasing complexity and cost.

2. Increased Operational Complexity: Inconsistent system configurations across the networks create potential security issues, significantly complicating efforts to apply uniform operational policies and streamline enterprise-wide management.

3. Inefficient Resource Utilization: The inability to leverage a common architecture prevents the USAF from achieving economies of scale in procurement, licensing, and workforce management.

4. Delayed Modernization: The operational drag caused by managing these disparate systems slows the adoption of new technologies and capabilities, such as advanced cloud integration and data center optimization.

Additional Technical Information:

To provide respondents with a more detailed understanding of the current "as-is" architecture, two (2) high-level Operational View (OV-1) diagrams representing the NIPR and SIPR ISN environments are available upon request. These documents are marked as Controlled Unclassified Information (CUI).

To receive these diagrams, interested parties must send a request via email to the Primary Point of Contact (POC) listed on this RFI. The subject line of the email should read: "Request for ISN- M RFI OV-1 Diagrams." The body of the email must include the requesting company's full name and active CAGE code.

Upon receipt and verification of the request, the CUI documents will be transmitted securely to the requesting party via DoD SAFE. By requesting these documents, the contractor attests that their information systems are compliant with the requirements for handling CUI. Please allow up to two (2) business days for a response.

Objective The goal of this RFI is to identify solutions to bring the system baselines of these two infrastructures into a single, modern, and consistent technical architecture. This initiative seeks to eliminate the existing inconsistencies, thereby optimizing performance, strengthening the overall security posture, and realizing significant and sustainable cost savings for the USAF.

Contracting Activity The Contracting organization responsible for this RFI is Department of the Air Force Material Command (AFMC) Department of the Air Force Life Cycle Management Center (AFLCMC), Air Force Program Executive Office (PEO) Enterprise IT and Cyber Infrastructure Division (AFLCMC/HNI), Contracting Office (AFLCMC/HNIK), 3 Eglin St, BLDG 1612, Hanscom

AFB, MA 01731.

Industry Responses Submission Guidelines and Instructions

Interested parties are invited to submit a response to this Request for Information (RFI). All submissions should adhere to the guidelines and instructions outlined below to ensure an efficient review process.

Schedule and Deadlines

1. RFI Questions Deadline: All questions regarding the content or requirements of this RFI must be submitted via email no later than April 17, 2026, at 3:00 PM EDT. The Government will provide a consolidated response to all questions received to all registered parties.

2. RFI Response Deadline: All final responses must be received no later than May 8, 2026, at 3:00 PM EDT. Submissions received after this deadline may not be considered.

Response Format and Structure To facilitate an effective review, responses must comply with the following formatting requirements:

1. File Format: Submissions shall be in a single, searchable PDF document.

2. Length: Responses should be as concise as possible. It is recommended not to exceed the specified pages (excluding cover page, table of contents, and appendices with pre-existing marketing materials).

3. Organization: The response shall be organized as follows:

a. Cover Page: Must include the RFI number, project title, vendor’s name, address, phone number, and primary point of contact.

b. Table of Contents.

c. Executive Summary: A brief (1-2 page) overview of the vendor’s key strengths as they pertain to this RFI.

d. Numbered Responses: Provide responses that are clearly numbered to correspond with the questions in this RFI. Questions should be restated before each answer.

Proprietary Information

Respondents are responsible for clearly marking all proprietary or confidential commercial information contained within their response. The Government will fully protect such information from unauthorized disclosure permitted by law. Information not marked as proprietary may be considered public information.

Please be advised that Government support contractors, including Advisory and Assistance Services (A&AS) contractors and personnel from Federally Funded Research and Development Centers (FFRDCs), such as The MITRE Corporation, may be utilized in the review of RFI responses. All non-Government advisors are required to appropriately protect any proprietary information submitted by respondents. Access to proprietary information will be restricted to only those individuals with a need-to-know.

Disclaimers

1. This RFI is issued solely for information and planning purposes and does not constitute a Request for Proposal (RFP), a solicitation, or an obligation to issue a future solicitation.

2. A response to this RFI is not an offer and cannot be accepted by the Government to form a binding contract.

3. The USAF will not provide reimbursement for any costs incurred in the preparation or submission of a response to this RFI. All costs associated with responding to this RFI will be solely at the interested party's expense.

4. Not responding to this RFI does not preclude participation in any future RFP, if one is issued.

5. The information provided in this RFI is subject to change and is not binding on the Government.

6. The Government has not formally established its contract strategy for this acquisition but is considering an approach for acquiring innovative and commercial solutions. While preserving the integrity of a competitive source selection is our objective, amongst others, Commercial Solutions Opening (CSO) or non-FAR-based procurements, including Other Transactions Authority (OTA), are under consideration. However, in finalizing our acquisition strategy as part of our market research and, based on the objectives outlined in the Government’s SOO, please identify potential contractual vehicles (both FAR and non-FAR based) and support details that may be available for use in this acquisition.

Point of Contact All communications, including the final submission and any questions concerning this RFI, must be directed in writing to Ms. Kathleen Delgado, Contracting Officer, at kathleen.delgado@us.af.mil.

RFI Questionnaire Company Information (1 Page Limit)

1. Company Name:

2. Cage Code:

3. Address:

4. Points of Contact:

5. Primary or applicable NAICS Code and corresponding business size:

6. Based on the above NAICS Code, state whether your Company is:

mailto:kathleen.delgado@us.af.mil

Small Business (Yes / No) Woman Owned Small Business (Yes / No) Small Disadvantaged Business (Yes / No) 8(a) Certified (Yes / No) HUBZone Certified (Yes / No) Veteran Owned Small Business (Yes / No) Service Disabled Veteran Small Business (Yes / No)

7. Please state your company’s status for the following:

Possesses a facility clearance at the Secret level (Yes / No) Employs personnel with active SIPRNet accounts (Yes / No) Has experience delivering Federal Information Processing Standard (FIPS) certified solutions (Yes / No)

8. Please identify your company as domestically or foreign owned (if foreign, please indicate the country of ownership).

9. Please identify your company’s existing DoD or GWAC contract vehicles with relevance to the requirements of this RFI.

Technical Questions (6 Page Limit)

1. Please provide a brief overview of your company, including the number of years in business, annual revenue, and total number of DoW customers.

2. What experience do you have in designing (modernizing and optimizing) existing network services infrastructure (Installation Service Nodes)?

3. Please provide a list of similar DoW projects you worked on, the service that you supported (USAF etc) and the names of the Government Program Managers.

4. Please provide a list of your key partnerships and certifications relevant to this project.

5. Describe your company’s approach to IT compute and storage modernization, cloud migration, and data center optimization.

6. Describe your company’s experience with network consolidation projects of similar scope and complexity. Please provide at least two case studies from the past three years, including challenges encountered and how they were resolved.

7. Describe your company's infrastructure pricing model (e.g., space, power, network connectivity, support).

8. Give an example of new and innovative services you added to a project based on its’ evolving requirements (focus on optimizing, modernizing and sustainment).

9. Describe your company’s approach for ensuring selected OEMs that can provide 24/7 online technical support, 4-hour response times, and the ability to deploy field technicians to all sites in the AF Enterprise

10. Describe your company’s approach for selecting OEM’s that rapidly publish patches and STIG Hardening Scripts as new cybersecurity vulnerabilities are discovered.

11. Describe how OEM components are evaluated to ensure they are FIPS 140-2 or 140-3 certified and on the Approved Products List (APL)