RFI Long Haul Transport_Final.pdf

REQUEST FOR INFORMATION

Tracking No.:822571938

The Continental United States (CONUS) North American Aerospace Defense Command (NORAD) Region, Air Forces Northern (CONR-AFNORTH), and Air Forces Space (AFSPACE) is seeking information on available transport solutions for secure and reliable end-to-end data transport across diverse formats and protocols.

THIS IS A REQUEST FOR INFORMATION (RFI) NOTICE ONLY. THIS IS NOT A REQUEST FOR

PROPOSALS (RFP). NO SOLICITATION IS AVAILABLE AT THIS TIME.

1. Overview/Purpose/Description of Procurement

The CONR-AFNORTH and AFSPACE are seeking information on available transport solutions for secure and reliable end-to-end data and voice transport across diverse formats and protocols. This RFI aims to gather information from industry leaders and innovators to inform our decision-making process for implementing a robust data transport solution. This RFI does not constitute a solicitation for proposals or bids.

2. Background/Scope of Effort

CONR-AFNORTH and AFSPACE requires a comprehensive data and voice transport solution capable of seamlessly handling a wide range of data formats and protocols, including legacy and modern systems.

The solution should facilitate secure and efficient data flow across our network, encompassing various endpoints and applications.

Our network infrastructure encompasses over 200 locations, including over 40 which could be categorized as CONUS isolated. CONUS isolated locations are typically minimally attended or unstaffed facilities situated 20-100 miles from populated areas, presenting unique connectivity challenges. While our preferred connectivity standard is 100 Mbps Internet Protocol (IP), solutions should accommodate a minimum bandwidth of 2 Mbps at austere locations. Data from certain facilities will be encrypted using National Security Agency (NSA) Type-1 certified devices, requiring seamless integration with such security measures. All interfaces/interconnections must be compliant with Committee on National Security Systems (CNSS) Policy-15 (https://www.cnss.gov/CNSS/issuances/Policies.cfm)

• Solutions must ensure redundant and resilient data transport to at least two separate CONR- AFNORTH data processing centers.

• Vendors should explicitly address how their solutions align with 0.9999 performance with less than 300 milliseconds latency and include Primary, Alternate, Contingency, & Emergency (PACE) planning principles, outlining specific mechanisms and diverse routing options (e.g., satellite, terrestrial, radio) to achieve redundancy and ensure continuous 24/7/365 operation even under adverse conditions.

• We are seeking a comprehensive end-to-end data transport solution that meets the requirements as specified in Sections 3.

3. Technical Requirements

This system requires robust data handling, security, and reliability, particularly in remote and challenging environments.

3.1 Data Handling:

• Diverse Format and Protocol Support: Must seamlessly handle serial Recommended Standard 232/532 (RS232/532), Internet Protocol Version 4/6 (IPv4/IPv6), Transmission Control Protocol (TCP) / User Datagram Protocol (UDP), voice over IP and Radio over IP (VoIP, RoIP).

• Specialized Protocol Integration: Full support for All Purpose Structured Eurocontrol Surveillance Information Exchange (ASTERIX) (including Federal Aviation Administration System Wide Information Management (SWIM) implementation) and MIL-STD 3011 Joint Range Extension Applications Protocol (JREAP).

• Protocol Conversion: Ability to translate between different data formats (e.g., RS232 to IP, ASTERIX to custom).

3.2 Resilience and Security:

• High Availability and Fault Tolerance: Minimize data loss and ensure continuous operation even with unreliable networks.

• Redundancy and Failover: Redundant connections from each remote location to at least two data centers with diverse routing (PACE implementation) for uninterrupted data flow.

• Data Security: Address security concerns in on-premises, cloud-based, or hybrid deployments, especially in remote and CONUS isolated environments. For cloud solutions, detail compliance with DoD Security Requirements Guides and Federal Risk and Authorization Management Program. (https://dodcio.defense.gov/library/)

3.3 Manageability and Scalability:

• Centralized Monitoring and Management: Real-time visibility into system performance, data flow, and potential issues across all locations.

• Scalability and Flexibility: Accommodate future data growth and incorporate new protocols and formats.

• Bandwidth Optimization: Employ data compression and prioritization for efficient bandwidth use in potentially constrained environments.

3.4 Deployment:

• Provide details on potential deployment models (on-premises, cloud-based, or hybrid), considering the challenges of remote and austere environments.

4. Information Requested

Please provide detailed information regarding your company and proposed solution, using the following subheadings:

4.1 Company Profile and Experience

• Overview of your organization, experience in data transport solutions for distributed and challenging environments, and relevant certifications.

4.2 Solution Description and Architecture

• Detailed description of your proposed data transport solution, including architecture, features, and capabilities, specifically addressing the redundancy, resilience, and security requirements.

4.3 Technical Specifications and Performance

• Information on supported hardware and software, data throughput rates, latency, and security protocols, emphasizing performance in bandwidth-constrained or unreliable network conditions.

4.4 Compliance, Security, and Certifications

• Detailed explanation of how the solution complies with Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIGs), Security Requirements Guide (SRGs) (https://public.cyber.mil/stigs/), and other relevant DoD cybersecurity mandates. Provide details on data encryption methods, key management, and access control mechanisms. Specify how the solution integrates with existing NSA Type-1 certified encryption devices.

4.5 Implementation, Training, and Support

• Details on implementation process, training, and ongoing technical support offerings, considering the geographical distribution of our network.

4.6 Pricing, Licensing, and Total Cost of Ownership

• Information on pricing models, licensing options, and estimated costs for implementation and maintenance, factoring in the scale and complexity of our network.

4.7 Case Studies and Relevant Experience

• Examples of successful implementations of similar data transport solutions in comparable DoD or government environments, highlighting key benefits and outcomes related to redundancy, reliability, performance, and security. Include specific examples of PACE implementation in challenging environments.

4.8 FAR and DoD Compliance Framework alignment for Technical Solutions

• Explain how your company ensures that the IT solution’s design, development, deployment, and maintenance of technical solutions complies with relevant Federal Acquisition Regulations (FAR) and Department of Defense Regulations Supplement (DFARS) for IT systems (e.g., FAR Part 12, FAR Part 39, FAR Part 52, DFARS 252.204-7012, DFARS 252.239-7010).

5. Company Information: Please provide the following information about your company:

• Company Name: Provide the full legal name of your company.

• Company UEI or CAGE: Provide the Unique Entity Identifier and/or Commercial and Government Entity (CAGE) Code.

• Physical Address: Provide the physical address of your company's headquarters or primary office.

• Point of Contact: Provide the name, phone number, and email address of the primary point of contact for your company.

• Business Type: Identify your company's business type, such as:

i. Small Business (if applicable, please specify the type, e.g. Small Disadvantaged Business, Woman-Owned Small Business, etc.)

ii. Large Business

iii. Non-Profit Organization

iv. Academic Institution

v. Other (please specify)

• Facility Clearance Level: Specify your company's current facility clearance level, if applicable.

Please provide the following details:

i. Clearance level (e.g. Top Secret, Secret, etc.)

ii. Date of last clearance verification

iii. Facility Clearance Agency (e.g. Defense Counterintelligence and Security Agency, etc.)

• Contract Vehicles: List all contract vehicles that would be available to the Government for the procurement of your products and/or services, such as:

i. General Services Administration Schedule

ii. Indefinite Delivery Indefinite Quantity contract

iii. Blanket Purchase Agreements

iv. Other (please specify)

Note: If your company has multiple contract vehicles, please list each one separately. If your company does not have any contract vehicles, please indicate "None" or provide an explanation.

6. Response Guidelines: Interested parties are requested to respond to this RFI with a white paper.

Submissions cannot exceed 20 pages (excluding diagrams or illustrations), single spaced, 12-point type with at least one-inch margins on 8 1/2” X 11” page size. The response should not exceed a 10 MB e-mail limit for all items associated with the RFI response. Responses must specifically describe the contractor’s capability to meet the requirements outlined in this RFI. Oral communications are not permissible.

SAM.gov will be the sole repository for all information related to this RFI.

Proprietary information and trade secrets, if any, must be clearly marked on all materials. 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 Systems Engineering and Technical Advisory contractor personnel reviewing submitted responses will have signed non-disclosure agreements and understand their responsibility for proper use and protection from unauthorized disclosure of proprietary information as described in section 41 of USC 423. The Government shall not be held liable for any damages incurred if proprietary information is not properly identified.

Companies who wish to respond to this RFI should send responses via email no later than May 19, 2025, 1700 CDT to kristin.s.martin2.civ@mail.mil and jessica.d.penick.civ@mail.mil.

7. Industry Discussions: Defense Information Systems Agency representatives may choose to meet with potential vendors and hold one-on-one discussions. Such discussions would only be intended to obtain mailto:kristin.s.martin2.civ@mail.mil further clarification of potential capability to meet the requirements, including any development and certification risks.

8. Questions: Questions regarding this announcement shall be submitted in writing by e-mail to kristin.s.martin2.civ@mail.mil and jessica.d.penick.civ@mail.mil. Verbal questions will NOT be accepted. Answers to questions will be posted to SAM.gov. The Government does not guarantee that questions received after May 02, 2025, at 1700 CDT will be answered. The Government will not reimburse companies for any costs associated with the submissions of their responses.

Disclaimer

This RFI is not a Request for Proposal (RFP) and is not to be construed as a commitment by the Government to issue a solicitation or award a contract. Responses will not be considered as proposals, nor will any award be made because of this synopsis.

All information contained in the RFI is preliminary as well as subject to modification and is in no way binding on the Government. FAR clause 52.215-3, “Request for Information or Solicitation for Planning Purposes”, is incorporated by reference in this RFI. The Government does not intend to pay for information received in response to this RFI. Responders to this invitation are solely responsible for all expenses associated with responding to this RFI. This RFI will be the basis for collecting information on capabilities available. This RFI is issued solely for information and planning purposes. Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received in this RFI that is marked “Proprietary” will be handled accordingly. Please be advised that all submissions become Government property and will not be returned nor will receipt be confirmed. In accordance with FAR 15.201(e), responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract.

mailto:kristin.s.martin2.civ@mail.mil