Request for Information - Local & Long-Distance Telecommunications Service - JBER, Alaska
Closed Special Notice Posted
Not the latest version. See the latest solicitation from .
- Agency
-
Pacific Air Forces
Air Force, Department of Defense
- Responses due
- Set-aside
- No set-aside
Opportunity facts
- NAICS code
- 517111 Wired Telecommunications Carriers
- Place of performance
- Jber, Alaska 99506, United States
Notice details come from SAM.gov. Updated .
About this opportunity
The Department of the Air Force Pacific Air Forces issued a Request for Information on commercial local and long-distance telecommunications services for Joint Base Elmendorf-Richardson, Alaska, with responses due July 7, 2026 at 2:00 PM Alaska Daylight Time. This RFI is market research only and does not constitute a solicitation, promise to solicit, or commitment to contract; the government is not accepting quotes at this time and will not reimburse response costs.
The Air Force seeks industry feedback on commercial pricing practices for local and international long-distance telecommunications to inform future acquisition strategy. The government requires 24/7/365 telecommunications services with 99.999% reliability supporting approximately 90,000 monthly call minutes across two Points of Presence at JBER. The requirement includes 40,100 Direct Inward Dialing numbers, minimum 192 concurrent calls per location using PCMU-8000/G.711 codec at 80 kbps, Session Initiation Protocol trunking, and integration with existing Unified Communications systems. A critical planning constraint exists: the government strongly prefers Firm-Fixed-Price structures but faces a challenge because destination countries vary significantly with distinct long-distance rates, complicating traditional FFP pricing. The contractor must submit an Installation and Cutover Plan within five working days of award with a 30-day implementation window. Service response requirements are tiered by outage priority: High Priority (one-hour on-site response), Medium Priority (four-hour response), and Low Priority (three working-day response). The Performance Work Statement is attached as a draft document.
Notice text
Subject: Request for Information (RFI) – Commercial Local and Long-Distance Telecommunications Services
Agency/Office: Department of War / 673 CONS/PKC
Notice Type: Request for Information
Response Date: 7 July 2026 at 2:00PM Alaska Daylight Time
Disclaimer
This RFI is issued solely for market research. It does not constitute a solicitation (Request for Quotations) or a promise to issue a solicitation in the future. This RFI does not commit the Government to contract for any supply or service whatsoever. Furthermore, the Government is not at this time seeking quotes and will not accept unsolicited quotes. Respondents are advised that the 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.
1.0 Purpose
This RFI is issued solely for information and planning purposes pursuant to Federal Acquisition Regulation (FAR) Part 10, Market Research. It does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. The Government is seeking industry feedback on commercial pricing practices for local and international long-distance telecommunications services to inform a future acquisition strategy.
2.0 Background
The Government requires reliable local and long-distance telecommunications services to support mission-critical operations. The Government’s strong preference is to utilize a Firm-Fixed-Price (FFP) Contract Line Item Number (CLIN) structure to the maximum extent practicable. The Government possesses historical data establishing the average monthly volume (in minutes) of long-distance calls. However, destination countries vary significantly, and each country carries a distinct long-distance rate, presenting a challenge for traditional FFP structuring.
3.0 Requested Information / Questions to Industry
The Government requests that interested vendors review the scenario above and provide responses to the following inquiries regarding commercial best practices:
Question 1:
The Government intends to utilize an FFP contract type. How does your company typically structure CLINs to bill for a combination of standard local services and variable long-distance (domestic and international) services in commercial contracts?
Answer:
Question 2:
The Government knows the historical average of monthly long-distance minutes but understands rates fluctuate based on the specific destination country. If this is the case, how would industry recommend structuring an FFP CLIN to account for this variation? Please discuss methods such as a single blended rate, geographic tiering (e.g., grouping countries by rate bands), baseline volume pricing with pre-priced overages, or other standard commercial practices.
Answer:
Question 3:
If a pure FFP structure for international long-distance is not standard commercial practice due to rate volatility, what alternative pricing structures or hybrid approaches (e.g., FFP for local or domestic combined with a draw-down or catalog approach for international) do you recommend while still providing cost predictability for the Government?
Answer:
Question 4:
To provide an accurate FFP quote or establish a reliable blended or tiered rate for international long-distance, what specific historical data elements (e.g., exact minutes per specific country, historical routing, time-of-day data, average call duration) would your company require the Government to provide in a future solicitation
Answer:
Question 5:
If a phased transition is expected, how does your firm typically bill for transition and parallel service periods and how do you mitigate dual-billing (paying the incumbent and the new provider simultaneously) during this phased cutover?
Answer:
Question 6:
What are your standard lead times for Local Number Portability (LNP) and Direct Inward Dialing (DID) block porting and how do you handle temporary call routing during the cutover window to prevent dropped calls or service interruption?
Answer:
Question 7:
What physical or logical infrastructure do you expect the Government to provide at the demarcation point prior to service initiation?
Answer:
Question 8:
What standard commercial Service Level Agreements (SLAs) do you offer for local and long-distance availability or uptime, and how are SLA failures mapped to financial credits or bill adjustments under the standard commercial agreements?
Answer:
4.0 Submission Instructions
Interested parties are requested to submit a capability statement and responses to the questions above.
Submit in PDF or Microsoft Word format with a maximum 10 pages, minimum 11 point font to Mr. Clay Schott at clay.schott@us.af.mil and Ms. Hannah Tolbert at hannah.tolbert.1@us.af.mil. Include company name, CAGE code, UEI, point of contact, and business size standard under NAICS 517111.
Submissions are due no later than 7 July 2026 at 2:00PM Alaska Daylight Time.
Files
| File | Type | Posted |
|---|---|---|
| LTTS Performance Work Statement (PWS)11 Jun 2026)_draft.docx | DOCX document | |
| LTTS Performance Work Statement (PWS)11 Jun 2026)_draft.docx | DOCX document |
Notice history
| Notice | Type | Posted |
|---|---|---|
| Local & Long-Distance Telecommunications Service - Joint Base Elmendorf-Richardson, Alaska - Amendment 1 | Solicitation | |
| This notice | Special Notice | |
| Local & Long-Distance Telecommunications Service - Joint Base Elmendorf-Richardson, Alaska | Pre-Solicitation |
Similar open opportunities
| Opportunity | Agency | Set-aside | Responses due |
|---|---|---|---|
| Amendment 0001 | Defense Information Systems Agency | Total Small Business | |
| RFQ: Reaward a 100MB commercial circuit Intra-SWA. | Defense Information Systems Agency | No set-aside | |
| RFQ: Start a 100 MB commercial circuit Intra-SWA. | Defense Information Systems Agency | No set-aside | |
| RFQ: Start a 1GB commercial circuit Intra-Europe. | Defense Information Systems Agency | No set-aside |
On GovTribe
Work this opportunity
- Track it in your pipeline
- Find teaming partners
- Similar opportunities
- Ask GovTribe AI about this opportunity