USAF WAN RFI_REV2.PDF
PDF 401 KB Posted
- Solicitation number
- Not on record
- Issued by
-
Department of Defense
About this file
This is a Request for Information (RFI) issued by the Air Force Life Cycle Management Center (AFLCMC) seeking market research on Wide Area Network (WAN) solutions and integration services.
AFLCMC requires establishment of a Wide Area Network comprising layer 2 and layer 3 transport services connecting 50 or more government and commercial sites, including cloud data centers, SATCOM facilities, and Defense Industrial Base partners. The network must support varying service level agreements and connectivity needs across sites, with some requiring up to 100 Gbps service with high availability and diverse redundant fiber paths, while others need lower bandwidth with reduced availability requirements. The contractor would serve as integrator, procuring and installing end-devices at government and commercial facilities, operating the network, providing upgrade recommendations, and managing lifecycle of both contractor-procured and government-owned endpoints. White paper responses in Microsoft Word are due no later than May 21, 2026, at 4:00 PM EST, submitted via email to taylor.wilson.6@us.af.mil. Section 1 must include administrative information including company name, address, point of contact, website, CAGE/DUNS/UEI, recommended contracting strategy, and business type classification under NAICS code 517111. Section 2, limited to 10 pages, must address technical capabilities including layer 2/3 service offerings, integration approach, contract recommendations, encryption experience (IPsec/MACsec), SLA definitions and timelines, private cloud connectivity options, SD-WAN capability, automation leveraging, fiber path diversity validation, management layer security, traffic isolation methods, Network Operations Center support, response times, and customer references. The accompanying draft Statement of Objectives outlines requirements for network transport supporting up to 100 Gbps with IPsec and MACsec capability, dedicated circuit extensions with diverse pathways, testing per acceptance test plan, 99.99% availability SLA with 4-hour mean time to repair, 9,000-byte MTU jumbo frames, 24/7 Network Operations Center support, NSA compliance including MACsec encryption and management plane security, and quarterly technical data package deliverables with complete architectural documentation and configuration files.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| USAF WAN RFI.PDF |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
UNCLASSIFIED
USAF Wide Area Network (WAN) Request for Information (RFI)
User Story: AFLCMC has a requirement to stand-up a Wide Area Network (WAN) of layer 2 and layer 3 transport services to connect 50 or more sites of government and commercial facilities (ex. cloud data centers, SATCOM, and DI8 partners). Each connected site will require varying service level agreements and connectivity needs to other sites. For example, site A may need 100 Gbps service, high availability, and jumbo frames to site B, but 1 Gbps service with low availability to all other connected sites. Some sites may require redundant and diverse fiber paths to ensure high availability and resiliency. The endpoints of the WAN should allow multiple separated networks to utilize the same network transport services. The integrator would procure and integrate end-devices and coordinate installations within government and commercial facilities. The Integrator would operate the network and provide recommendations to the government for upgrades and configuration changes. The Integrator would manage, maintain, and recapitalize the contractor-procured and government-owned endpoints.
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 Air Force is not at this time seeking proposals and will not accept unsolicited proposals. Respondees 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 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. If a solicitation is released, it will be synopsized on the SAM.gov website.
It is the responsibility of the potential offerors to monitor this site for additional information pertaining to this requirement.
Notice of Non-Government Advisors: The Government intends to utilize non government advisors to assist in the review and technical analysis of responses received under this RFI. This support is strictly for the purpose of market research, technical feasibility assessment, and the refinement of future requirements. All advisors shall comply with procurement integrity laws and shall sign Non-Disclosure Agreements and Rules of Conduct/Conflict of Interest statements. The Government shall take into consideration requirements for avoiding conflicts of interest and ensure advisors comply with safeguarding proprietary data. Submissions in response to this RFI constitute approval to release the submittal to necessary Government Support Contractors to include Modern Technology Solutions, Inc. (MTSI), and The MITRE Corporation.
Submission Instructions:
1. Interested parties are requested to respond to this RFI with a white paper.
2. White papers in Microsoft Word are due no later than 21 May 2026, 16:00 EST.
Responses shall be submitted via e-mail only to taylor.wilson.6@us.af.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.
3. Any questions regarding this RFl shall be sent to the same personnel mentioned above.
4. Section 1 of the white paper shall provide administrative information, and shall include the following as a minimum:
a. Company name
b. Company Address
c. Point of Contact Phone and Email Address
d. Website Address
e. CAGE, DUNSorUEl
f. Recommended contracting strategy
g. Business type (large business, small business, small disadvantaged business, 8(a)-certified small disadvantaged business, H U BZone small business, woman-owned small business, service-disabled veteran-owned small business) based upon North American Industry Classification System (NAICS) code 517111. "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
5. Section 2 of the white paper shall answer the questions addressed below and shall be limited to 10 pages.
Questions:
• Is your company capable of both providing layer 2 or layer 3 transport services and serving as an integrator? If not, how do you envision teaming to accomplish the requirement?
o What types of Layer 2 (E-LINE, E-LAN, EVPL, VPLS) and Layer 3 (MPLS/SR) service do you offer?
o What hand-off options are supported (Ethernet, VLAN, QinQ, LACP, jumbo MTU)?
• Would you recommend establishing core nodes (e.g. within colocation facilities) or simply acquire layer 2 services between edge locations?
• What type of contract would you recommend?
• What experience do you have with IPsec, MACsec, or equivalent encryption?
• How would you define differing levels of service level agreements?
o Can you provide the set of SLAs you offer?
o What is your typical timeline for circuit provider installation or stand-up?
o How are SLA measurements performed? Can the customer validate?
o What are the credits/remedies for failure to meet SLAs?
• What options do you provide for private cloud connectivity?
• Is your network transport SD-WAN capable?
• How do you leverage automation in the network transport you provide?
• How would you determine and validate fiber path diversity for locations?
• How would you secure the management layer of this transport network?
• How is the network traffic traversing the solution isolated from other traffic?
• What kind of Network Operations Center or notification methods would you use for unplanned outages?
o What is your target response time? Provide a historical mean time to repair (MTTR) and outage data for similar networks.
• Can you provide references for customers with similar architectures?
• Is your company cleared to Top Secret material?
SOO Draft
1. Network Transport
1.1. The Contractor shall develop, install, deliver, and maintain a Wide Area Network (WAN). The WAN shall support up to 100 Gigabits per second (Gbps) transfer speeds, have the ability to support Internet Protocol Security (IPsec) and Media Access Control Security (MACsec), and enable exchange points with other network fabrics (to be defined).
1.2. The Contractor shall deploy dedicated circuit network extensions of the WAN to sites identified by the United States Government (USG). The Contractor shall procure circuits that may require diverse and redundant pathways to the USG identified sites. Where existing government connectivity exists, the circuits shall be diverse from existing government connectivity. The network extensions shall be I Gbps, 10 Gbps, or 100 Gbps capable as identified by the USG. Sites identified for a network extension may be in or out of CON US. The Contractor shall coordinate with communications squadrons or local networking authorities to install new circuits and map fiber to USG identified sites to include site surveys addressing power and rack requirements. The WAN-edge end devices installed at the USG site shall include networking hardware to connect to multiple cryptographically separated USG networks. The handoff will be an ethernet port at the specified bandwidth. USG devices beyond the WAN-edge device at the site are out of scope.
1.3. The Contractor shall define network architecture and design needs for new sites.
The WAN shall integrate with non-traditional architectures and terrestrial and non-terrestrial options. New sites may require networking hubs with further extensions across a campus.
1.4. The Contractor shall monitor and manage end of life/support schedules for existing sites, and accordingly plan for required technical refreshes.
1.5. The Contractor shall procure and manage the lifecycle of required circuits.
1.6. The Contractor shall have the ability to procure and/or manage various circuit types (Commercial, DISA, etc.).
2. Testing
2.1 . The Contractor shall test the WAN connectivity and new network extensions to ensure high performance for the users. The tests shall measure Latency, Jitter, Packet Loss, and other variables in accordance with the Acceptance Test Plan.
The testing capabilities should be sufficient to assess network health and inform forecasting of future requirements.
3. Quality of Service
3.1 . The WAN shall meet the following Service Level Agreement (SLA):
3.1.1. Availability: 99.99%
3.1.2. Time to Restore / MTTR: Restore within 4 hours
3.1.3. MTU: --9000 bytes
3.1.3.1. The Contractor shall define the MTU settings that prevent packet fragmentation. They shall define what layers of packet header overlays exist in the architecture.
3.1.4. Specified per link
3.1.4.1. Latency:
3.1.4.2. Jitter:
3.1.4.3. Packet Loss:
3.1.4.4. Throughput:
3.2. The network extensions shall meet SLA requirements set by USG. Network extensions may be set as high as 100Gbps or lower.
3.3. The Contractor shall identify what USC dependencies may affect availability.
3.4. The Contractor shall stand up a Network Operations Center (NOC) to monitor, control, configure, and manage the transport network. The NOC shall provide 24/7 support via a phone line and online portal to the USC. The Contractor shall provide reports and/or live dashboard(s) on the following network characteristics (not all inclusive):
3.4.1. Bandwidth usage
3.4.2. Network health
3.4.3. Top sites
3.5. The Contractor shall provide on-call networking personnel to lead troubleshooting and travel to affected sites as necessary. All Contractor travel CONUS/OCONUS will be approved by the USC.
3.6. The Contractor shall provide redundant capability at sites to conduct maintenance and fail over with no impact to users.
3.7. The Contractor shall provision services to newly identified sites within TBD weeks/months.
4. Compliance
4.1. The WAN core shall be Media Access Control Security (MACsec) encryption capable.
4.2. The Contractor shall ensure the WAN is compliant with all National Security
Administration (NSA) directives and USC policy.
4.2.1. Management Plane Security (AAA, RBAC, TACACS/RADIUS)
4.2.2. Encryption Requirements
4.2.3. Secure Supply Chain
4.2.4. Logging, SIEM Integration, Retention Requirements
4.3. The Contractor shall provide all artifacts required to receive an Authorization to Operate (ATO) and maintain accreditation.
5. Support
5.1. The Contractor shall ensure the WAN is scalable to add new sites as the USG requires.
5.2. The Contractor shall define and implement a change management process. The
WAN infrastructure and all sites shall be mapped out in a clear architecture that is maintained.
6. Deliverables
6.1. Monthly Status Reports (MSR)
6.1.1. Progress of installs, upcoming tech refresh needs, performance metrics, etc.
6.2. Schedule
6.2.1. Installs and site updates
6.3. Technical Data Package (TDP) - quarterly updates
6.4. Contractor Funds Status Report (CFSR)
6.5. Funds & Man-hours Expenditure Report (F&MHER)
6.6. Government Furnished Equipment (GFE) - quarterly updates
6.7. PLACEHOLDER: CDRL for dashboards & ctr-owned repositories
7. Data Rights 7.1.The Government desires Unlimited Rights for all hardware, software, and deliverables under this contract.
7.2. The Contractor shall provide a comprehensive Technical Data Package (TDP) for each site/node. The TDP shall include complete architectural documentation with physical and logical topology of the network.
7.3. The Contractor shall provide all configuration files for the network hardware (ex.
routers, firewalls).
8. Period of Performance
8.1.TBD
9. Place of Performance 9.1.Work shall be performed at various CONUS and OCONUS locations.
10. Government Furnished Equipment
10.1 .The Government will provide access to necessary classified and unclassified systems required for communications.
I 0.2.The Government will provide Common Access Cards (CACs) for appropriate personnel to facilitate communications and access for installs.
I 0.3.The Contractor shall own the lifecycle management of all government furnished equipment, and maintain necessary stock required for installs, technical refreshes, and break/fix requirements from procurement and storage through decommission/destruction. They shall track and report on GFE as required by
USG.
10.4.The Contractor shall manage all licenses and warranties pertaining to the Government Furnished Equipment.
| Page 1 |
| Page 2 |
| Page 3 |
| Page 4 |
| Page 5 |
File details come from the government source that posted it. Updated .