Defense Research and Engineering Network (DREN), 5

Questions & Answers / Clarifications

This document contains questions submitted by industry regarding the DREN 5 RFI and the Government's responses. It aims to solicit industry recommendations on how best to procure, implement, and operate DREN 5, addressing challenges and exploring potential acquisition strategies.

• Transition Management: The Government is open to considering all industry recommendations for a dedicated, independently-contracted Transition Management function, separate from incumbent and follow-on performers. Proposals from firms focused on acquisition and program integration will be evaluated.
• End-to-End SLA Compliance: For a multiple-contract model, the Government is seeking industry recommendations on tools and approaches to best enable high-level end-to-end service and cooperative testing among multiple providers, particularly for assigning accountability for SLA compliance across contract boundaries.
• Small Business Set-Asides: The Government will utilize small business responses and market research to determine how best to utilize small business talents. They will adhere to FAR 52.219-14, "Limitations on Subcontracting," and encourage small businesses to articulate their roles and intent to offer.
• Supply Chain Risk Management (SCRM): Specific security requirements, including real-time country-of-origin tracking or enhanced verification beyond self-certification, are not known at this time and will be specified in future Request for Proposal (RFP) documentation.
• International Connectivity: The Government has no pre-conceived notion on how to procure international connectivity and encourages respondents to articulate the approach that best advantages the Government.
• Response Guidelines: Responses to the RFI are limited to 25 pages. Industry does not need to repeat or address each question individually; the questions should guide recommendations.
• Network Architecture & Functionality: The Government welcomes industry input on network architectures, where functionality should reside (core vs. edge), and the evolution of management, automation, routing, and peering for DREN 5. There have been no predeterminations regarding DREN 5's network architecture.
• Small Business Set-Asides (MBEs): The Government has not determined any set-asides at this time, including for MBEs.

These Q&As provide significant insight into the Government's considerations for the DREN 5 procurement strategy, particularly regarding contract structure, integration, small business participation, and technical approaches. Bidders should use this information to inform their recommendations and potential proposals. Specific security requirements and detailed technical specifications will be provided in future RFP documentation.

Request for Information (RFI)

This RFI seeks industry input to aid in the planning and development of a potential new requirement for the Defense Research and Engineering Network (DREN). The DREN has served as the Wide Area Network for the Department of Defense’s High Performance Computing Modernization Program for nearly three decades, providing high bandwidth, low latency communications. This RFI is specifically for planning purposes and is NOT a Request for Proposals (RFP).

The DREN has grown significantly in terms of connected sites and bandwidth since its inception. The current contract structure, with a ten-year performance period, consumes a substantial portion of its term in transition activities. The Program Management Office (PMO) is exploring alternative acquisition strategies to address this transition burden.

The Government is evaluating two primary acquisition approaches for DREN 5:

1. A single-award contract.
2. Multiple contracts covering discrete functional component areas (e.g., transmission circuits, carrier-neutral data centers, network operations center services, technical services).

Respondents are requested to provide comments on the advantages and challenges of a multiple contract procurement model. Specific questions are posed regarding:

• DREN Acquisition Approach: Recommended contract groupings, suitability of multi-award contracts, best approach for managing seamless integration, and opportunities for Small Business participation.

• Transmission Circuits: Structuring acquisitions for competition, combining circuit types, engaging international providers, recommended bandwidths, connectivity approaches for >100G, pricing methodologies, installation timelines, recommended circuit technologies, shared vs. dedicated infrastructure, SLA standards, challenges in end-to-end network provision, circuit term lengths, and Small Business set-aside opportunities.

• Carrier Neutral Data Centers (CNDC): Recommended acquisition strategies, considerations for non-neutral centers, factors for DCNs at government bases, available industry services, minimizing cross-connect costs, meeting DoD security standards, anticipated volume discounts, and Small Business set-aside opportunities.

• Nodal/Site Equipment: Ensuring hardware/software relevancy and licensing, benefits of purchasing vs. leasing, obtaining Tier 3 support, cost-effective acquisition structures, and recommended staging/installation processes.

• Network Operation Center (NOC): In-sourcing vs. out-sourcing, tools/processes for customer support, strategies for security/compliance/resiliency, implementation timelines, challenging requirements, access/tools for monitoring, and Small Business set-aside opportunities.

• Technical Services: Whether to include with component procurements or procure separately, and Small Business set-aside opportunities.

• Submit a white paper, not exceeding 25 single-spaced pages (11-point type, 1-inch margins).

• Email submission limit: 5 MB.

• Responses due by 1:00 PM CT, April 20, 2026.

• Submit via email to Ms. Katie Day (katie.s.day.civ@mail.mil) and Ms. Amber McKee (amber.m.mckee4.civ@mail.mil).

• Questions due by email by April 6, 2026.

• No reimbursement for response costs.

This RFI is for information and planning purposes only and does not constitute a commitment to issue a solicitation or award a contract. Responses are not proposals.