Attachment 3 Q_A_Government Responses.pdf
PDF 142 KB Posted
- Solicitation number
- FA301626Q0004
About this file
This is a Questions and Answers (Q&A) document for federal contract opportunity FA301626Q0004, issued on April 9, 2026, for Local Telecommunications Services (LTS) at JBSA Lackland and Fort Sam Houston. The document contains 53 numbered questions submitted by contractors and corresponding government responses addressing the Performance Work Statement (PWS) requirements.
The contract requires vendors to provide Session Initiation Protocol (SIP) trunking with Primary Rate Interface (PRI) handoff, including all necessary equipment and materials. Key service requirements include: porting 40,000 DID numbers at JBSA Lackland and 60,000 DID numbers at Fort Sam Houston (segmented by site) by August 31, 2026; providing unlimited domestic long distance services at a flat rate; offering international long distance services billed on a per-minute basis rather than per-call; and providing E911 capability diagrams without connection to existing base emergency response systems. The vendor must manage SIP-to-PRI internetworking and session border controllers. The government clarified that no parallel operating period is required during transition from legacy Nortel CS2100 systems, no diverse path requirements exist, and no mission-critical or life-safety cutovers are involved. The contract is structured as firm fixed-price with no anticipated growth requirements. The quote deadline was extended to April 28, 2026, at 2:00 PM CST under Amendment 0002, with all infrastructure required to be in place by August 31, 2026. Multiple questions resulted in PWS modifications, including removal of diversity verbiage and clarification on numbering segmentation and DID counts.
View the file
Other files
Show all 13
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
TOPR NO.:
PROJECT NAME
DATE:
CONTRACTOR
NUMBER QUESTIONS PWS REFERENCE GOVERNMENT RESPONSE GOVERNMENT REFERENCE DOES IT CHANGE PWS Y/N
Can the governement confirm that “Attachment 4-UAR” is only required for individuals who do not have base access but want to attend the April 7th site survey. If the UAR is required for everyone, what information should be placed in Blocks 1-13 for the sponsor?
Attachment 4-UAR
UAR is required for individuals who do not have an active contractor CAC. Since site visit has already passed, UAR will be required for those who perform work that do not meet the previously mentioned contractor CAC.
UAR No
2 PWS; Session Initiation Protocol (SIP) trunking with a Primary Rate Interface (PRI) hand-off. Will the vendor need to provide the router? 5.2; 5.6.1 Vendor will need to provide all equipment and material necessary for SIP trunking with PRI handoff 2.0, 5.1, 6.1 PWS No
3 If a router needs to be provided, does the base plan to own at end of service or can it be bundled with the managed service? 5.2; 5.6.1 The Base will not take ownership or have any service responsibility 2.0, 5.1, 6.1 PWS No
4 Does the base have equipment for 1G and 10M to support the Transport channels noted? 5.2; 5.6.1 Vendor will need to provide all equipment and material necessary for SIP trunking with PRI handoff 2.0, 5.1, 6.1 PWS No
5 Is there any flexiblity with this - Contractor will port all NPA-NXX DID numbers within 30 days of contract start date 5.2.1 Vendor need to have all numbers ported no later than 31
Aug 2026 5.2.1 PWS Yes
6 How many domestic long distance are used? On-net to on-net is included. 5.2.1 Vendor will provide SIP trunking with Long Distance Services for all DID numbers 2.0, 5.1, 6.1 PWS No
To confirm compliance, should the contractor assume responsibility for SIP-to-PRI internetworking, including media gateway provisioning, or will Government-Furnished-Equipment be provided for PRI termination?
5.1 Paragraph 2 Vendor will need to provide all equipment and material necessary for SIP trunking with PRI handoff 2.0, 5.1, 6.1 PWS No
8 In section 5.2.1 of PWS, it states SIP Signaling will be used, but scope states SIP with PRI/TDM handoff. Please confirm requirement 5.2.1 Vendor will provide SIP trunking with PRI handoff 5.1, 6.1 PWS No
9 Can the base confirm if the preferred Ethernet handoff is 1000Base SMF (optical)? 5.1 Paragraph 2 Vendor will need to provide all equipment and material necessary for SIP trunking with PRI handoff 2.0, 5.1, 6.1 PWS No
During transition from the Nortel CS2100 system to CUCM, should the contractor plan for a parallel operating period supporting both platforms, and if so, is a specific duration anticipated?
5.1 Paragraph 2
Vendors should not plan for a parallel operating period supporting both platforms. Therefore there is no specific duration
5.1 PWS
6.1 PWS No
When you state diverse and active paths, I am reading that as physically diverse routes, separate POPs, and active/active (not primary/backup).
Does this sound correct or are you just asking for logical diversity?
5.1 Paragraph 2 No diverse path needed.
PWS at 5.1 & 6.1 has been edited to remove verbiage
5.1 PWS
6.1 PWS Yes
12 On the diversity request, are there existing dual entrances? 5.1 Paragraph 2 See answer given to question 11 5.1 PWS
6.1 PWS Yes
13 Does the base have equipment for 1G and 10M to support the Transport channels noted? 5.4, 6.4 Vendor will need to provide all equipment and material necessary for SIP trunking with PRI handoff 2.0, 5.1, 6.1 PWS No
14 Will base accept a replacement product for analog services? 5.4, 6.3 Yes 6.3 PWS No
15 Is it possible to identify what lines are used for? i.e fax, elevator, alarm, modem, voice 5.4, 6.3 Goververment is not able to identify specific use of each line 5.4, 6.3 PWS No
16 Can the analog flex voice lines be ported over as DID? 6.3 Each analog line per PWS needs to be cutover 6.3 PWS No
Does the Government require the two (2) Fort Sam Houston locations to be diverse and redundant from one another, and additionally to be diverse and redundant from the IPVPN circuits at JBSA Lackland? Please provide detailed guidance on acceptable diversity and redundancy (e.g., carrier diversity, physical route diversity, equipment/location separation, or service level redundancy).
App 1A PWS 5.1; App 1B PWS 6.1 See answer given to question 11 App 1A PWS 5.1; App 1B PWS 6.1 Yes
18 Does the Government require geographically diverse softswitch or call routing platforms to support survivability during site wide outages?
App 1A PWS 5.1; App
1B PWS 6.1 No App 1A PWS 5.1; App 1B PWS 6.1 No
Please clarify whether transport channels referenced in the PWS are required to be physically diverse from other Government network services (e.g., base IPVPN or DISN connections).
App 1A PWS 5.4; App 1B PWS 6.4 See answer given to question 11 App 1A PWS 5.4; App 1B PWS 6.4 Yes
QUESTIONS/RFI's & ANSWERS (Q&A)
FA301626Q0004
LTS for JBSA Lackland and Ft Sam Houston 9-Apr-2026
Are there specific availability or uptime requirements (e.g., 99.9%, 99.99%) for local voice services beyond standard commercial best effort expectations?
PWS 2.1 PWS 2.2.1 provides guidance 2.2.1 PWS No
Ft. Sam Houston has its own PRI counts and Central Control Points (CCPs) identified in the PWS. Do both Fort Sam Houston locations require access to the full inventory of approximately 60,000 telephone numbers, or should numbering be segmented by site?
App 1B PWS 6.1 Numbering should be segement by site 6.2 PWS Yes
22 Based on the DIDs listed for JBSA Ft. Sam Houston, which telephone numbers are associated with Brooke Army Medical Center (BAMC)? App 1B PWS 6.2 210-539-0000-9999 & 210-916-0000-9999 6.2 PWS Yes
Does the Government require SIP trunking to interoperate with any existing Government owned call managers, Session Border Controllers (SBCs), or legacy TDM infrastructure, and if so, please identify the platforms and handoff requirements.
App 1A PWS 5.6; App
1B PWS 6.6
Vendor will need to provide all equipment and material necessary for SIP trunking with PRI handoff 2.0, 5.1, 6.1 PWS No
Please clarify whether the Government requires the Contractor to provide and manage SBCs as part of the LTS solution, or if SBCs will be Government furnished equipment.
App 1A PWS 5.6; App 1B PWS 6.6 Contract should provide and manage SIP to PRI 5.1, 6.1 PWS Yes
25 Are there mission critical or life safety lines at Ft. Sam Houston that require zero interruption cutovers? App 1B PWS 6.3 No there will be no Mission Critical or Life-Safety Cutovers involved in the requirement App 1B PWS 6.3 No
The PWS indicates that all telephone numbers must be ported within thirty
(30) days of contract start. Does this timeline assume all prerequisite activities (e.g., LOAs, external carrier coordination, site readiness, and testing) are completed prior to Day 1? Would the Government consider a phased or mutually agreed porting schedule that prioritizes mission critical numbers and ensures service continuity?
App 1A PWS 5.2.1;
App 1B PWS 6.2.1
Vendor need to have all numbers ported no later than 31 Aug 2026 5.2.1, 6.2.1 PWS Yes
Does the Government require number portability for future acquisitions, deactivations, or reorganizations occurring after the initial thirty day transition window?
N/A N/A N/A No
Can the Government clarify the types of systems and services supported by the Commercial Service Locations (CSLs) identified in the PWS, including whether CSLs support alarm circuits, elevator phones, fire alarms, security cameras, access control systems, life safety systems, or other regulated or operational technologies?
App 1B PWS 6.3 N/A N/A No
Are any circuits required to support Quality of Service (QoS) marking or traffic prioritization across Government networks, and if so, what standards or policies should be applied?
App 1A PWS 5.6; App 1B PWS 6.6 No N/A No
Does the Government require call detail records (CDRs) or usage reporting beyond standard domestic long distance summaries, and if so, at what frequency and level of detail?
App 1A PWS 5.2.1;
App 1B PWS 6.2.1
Customer Service Records (CSR) are identified in Pricing Schedule Attachment 2 Pricing Schedule No
31 Please provide the last six (6) months of Domestic Long Distance usage for JBSA Lackland, JBSA Ft. Sam Houston, and BAMC.
App 1A PWS 5.2.1;
App 1B PWS 6.2.1 N/A N/A No
Please clarify whether E911 services must integrate with any existing base emergency response systems or third party Public Safety Answering Points (PSAPs).
App 1A PWS 5.5; App
1B PWS 6.5
There will be no connection with the exisiting base emergency response systems or third party Public Safety
Answering Points (PSAPs) N/A No
33 Are there specific testing, validation, or acceptance criteria the Government intends to apply prior to cutover completion at each site? PWS 4.2.1 No N/A No
Does the Government anticipate any facility access restrictions (e.g., hours, escort requirements, blackout periods) that could impact installation or cutover activities?
PWS 3.1 No N/A No
Does the Government require Telecommunications Service Priority (TSP) for each circuit, and are restoration objectives required to be exercised or tested during the period of performance?
App 1A PWS 5.1; App 1B PWS 6.1 No. 2.1.4 PWS covers all outage priority expectations 2.1.4 PWS No
Please clarify whether any telephone numbers are associated with classified, restricted, or mission sensitive operations that require special handling during porting or maintenance.
N/A N/A N/A No
Are there anticipated growth requirements (add/move/change telephone numbers or circuits) during the period of performance, and is pricing expected to be fixed or usage based?
N/A No anticipated growth is expected.Contract will be deemed firm fixed-price N/A No
38 Does the Government require Contractor participation in base wide outage reporting, incident response, or communications exercises? PWS 2.1.3 2.1.1 and 2.1.3 PWS covers all outage expectations 2.1.1, 2.1.3 PWS No
Please confirm whether Contractor provided services must comply with any additional DoD or Air Force cybersecurity requirements beyond standard commercial voice offerings.
N/A None Apply N/A No
Is there a Government preferred sequence for site activation (JBSA Lackland vs. Ft. Sam Houston), or may the Contractor propose an optimized deployment schedule?
PWS 4.2 Contractor will provide proposed cutover plan for government review 4.2 PWS No
41 Would the Government be open to reviewing a contractor recommended CLIN structure aligned to the proposed solution and pricing strategy?
RFP Page 7;
Attachment 2 – Pricing
Schedule Yes. N/A No
Total DID is 40,000 vs the JBSA Attachment 2 Pricing schedule
20MAR2026 Row 22 & 23 has it as 400. Is the government intending to keep all 40,000 DID and correct the pricing schedule?
5.2 Yes, Gov will keep 40,000 DID's. Unit of issue is HD on
Pricing Schedule. 5.2 PWS No
43 Question: Could the government provide an estimated LD call volume per month 5.2.1 No N/A No
44 Access to International Long-Distance charged on a per-call basis. Could the provider bill on per minute rather than per call? 5.2.1 Yes the government will change PWS to reflect billing on a
Per-Minute basis 5.2.1 PWS Yes
45 Access to International Long-Distance charged on a per-call basis. Could the provider bill on per minute rather than per call? 5.2.1 Yes the government will change PWS to reflect billing on a
Per-Minute basis 5.2.1 PWS Yes
E911 Capability: is the government asking for basic 911 which provide address of caller or E911 which provide station information to include address, floor, and office/cube.
5.5 No Connection will be required to E911 System; However
E911 Capability diagrams needed 5.5 PWS No
Total DID is 60,000 vs the JBSA Attachment 2 Pricing schedule
20MAR2026 Row 55 & 56 has it as 600. Question: Is the government intending to keep all 60,000 DID and correct the pricing schedule.
6.2 Yes, Gov will keep 60,000 DID's. Unit of issue is HD on
Pricing Schedule. 6.2 PWS No
Unlimited Domestic Long Distance at a flat rate price included in the cost.
Question: Could the government provide estimated LD call volume per month.
6.2.1 No Government will not provide monthly call volume 6.2.1 PWS No
49 Access to International Long-Distance charged on a per-call basis. Could the provider bill on per minute rather than per call? 6.2.1 Yes the government will change PWS to reflect billing on a
Per-Minute basis 6.2.1 PWS Yes
50 Access to International Long-Distance charged on a per-call basis. Could the provider bill on per minute rather than per call? 6.2.1 Yes the government will change PWS to reflect billing on a
Per-Minute basis 6.2.1 PWS Yes
E911 Capability: is the government asking for basic 911 which provide address of caller or E911 which provide station information to include address, floor, and office/cube.
6.5 No Connection will be required to E911 System; However
E911 Capability diagrams needed 6.5 PWS No
Delivery Schedule: Can you government clarify the expected deliverable in sub factor 4? What is the expectation of the 30 day installation and cutover timeline delivery schedule? What are contractors expected to provide after
30 days?
Amendment 0001, The expectation is the contractor will have all infrastructure in place by the end of the specified deadline which will be amended in soliciation to reflect NLT 31 Aug 2026 Amendment 0002 N/A
With questions only being submitted April 9th, will the government allow a two week extension for contractors to review and update their responses to provide a competive and techical solution
General Government will extend quote deadline to 28 April 2026 @
2:00PM CST. Revision to quote deadline will be under Amendment 0002.
Amendment 0002 N/A
Questions
File details come from the government source that posted it. Updated .