Attachment 7 - LTS Q and A.pdf

DAFB Local Telecommunication Q&A

1. Does the Government require a SIP or PRI handoff?

Answer: The Government requires a PRI handoff. The existing Avaya switch infrastructure is configured for ISDN PRI and does not currently have a Session Border Controller (SBC) in place to support commercial native SIP trunking.

2. Can the existing CSL be converted to a DID? If not, would an LTE-based replacement solution be acceptable?

Answer: The existing Commercial Subscriber Line (CSL) is currently inactive and is not mapped to any active mission-essential devices. Offerors may propose an LTE-based replacement or alternative modern solution, which the Government will evaluate for technical acceptability.

3. What type of line is the referenced circuit (e.g., alarm, fire, modem)?

Answer: The referenced circuit (11.HFCU.447569) is an ISDN PRI (Primary Rate Interface) Trunk that connects to our Call Manager (CM) to support local dial tone, rather than an analog specialty line (such as an alarm, fire panel, or modem).

4. Is the designated Period of Performance (POP) firm?

Answer: Yes, the Period of Performance is firm as outlined in the solicitation.

5. PWS says the services include CONUS long-distance. Is there a requirement for OCONUS and international long-distance? If so, how should they be priced?

Answer: No. OCONUS and international long-distance are not part of this requirement. Price your proposal strictly for CONUS long-distance as outlined in the PWS and Quote Schedule.

6. PWS says the services include CONUS long-distance. Is there a set number of CONUS long-distance minutes that should be priced? If the requirement is for unlimited CONUS long-distance, can the Government provide records on CONUS long-distance for each of the last 12 months?

Answer: The requirement is for unlimited CONUS long-distance. We are gathering the last 12 months of usage records and will post them in an upcoming update to the solicitation.

7. Which Volume should include SF 1449 and the information required by RFO 52.212-1?

Answer: The signed SF 1449 and associated contract documents should be submitted in Volume III (Contract Documentation).

8. Does the Government want Offerors to submit all of pages accompanying the SF1449 or only those requiring offeror input?

Answer: Submit the signed SF 1449 cover page and any pages that require you to fill in information, certifications, or signatures. You do not need to return pages that do not require input.

9. Does the Government want Offerors to complete and submit the Supplies or Services & Prices or Costs table or is Attachment 2 the only pricing document required?

Answer: Please fill out and submit both. The pricing on the SF 1449 CLIN table and Attachment 2 (Quote Schedule) must match.

10. How many concurrent call paths are required?

Answer: The system is currently set up for 138 concurrent call paths across the six PRI trunks.

Your proposed solution needs to support this baseline.

11. Is the requirement for a Mission Essential Plan limited to just the elements listed in Section L, Subfactor 5, or is the Government expecting a complete Mission-Essential Contractor Services Plan as described in 252.237-7024 Notice of Continuation of Essential Contractor Services which is included by Full Text with the SF1449?

Answer: Offerors should submit a complete plan that addresses both the evaluation criteria in Section L (Subfactor 5) and the general requirements of the DFARS clause 252.237-7024 included in the solicitation.

12. Please provide the current incumbent CSR and circuit inventory for all services being replaced under this requirement.

Answer: The complete circuit inventory is detailed in Appendix 1 of the PWS. For security and administrative reasons, the full Customer Service Record (CSR) will not be released pre-award.

13. Please confirm the exact number of active ISDN PRIs and associated circuit IDs, as Appendix 1 appears to contain a duplicate entry.

Answer: The Government operates six (6) active ISDN PRIs. Offerors should price their solutions based on supporting exactly six (6) PRI trunks.

14. Please confirm whether all 6,000 DIDs listed in Appendix 1 must be ported at cutover.

Answer: Yes, all 6,000 DIDs listed in Appendix 1 are active and must be successfully ported at cutover.

15. Does the Government prefer continued PRI handoffs to the existing Avaya system, native SIP, or have no preference provided the proposed solution meets the PWS?

Answer: The Government requires a PRI handoff. The existing Avaya switch infrastructure is configured for ISDN PRI.

16. If SIP is proposed, does the Government currently have an EBC/SBC available for contractor interconnection?

Answer: No. The Government does not currently have a Session Border Controller (SBC) in place to support commercial native SIP trunking. Hand-offs must be PRI.

17. What is the maximum permissible service interruption during cutover, and does the Government prefer phased migration or a single cutover?

Answer: Specific migration preferences and cutover windows will be finalized with the awardee.

However, any service interruption must be minimized and scheduled during approved maintenance windows. Offerors should propose their best phased or flash-cutover technical approach for evaluation.

18. Will the Government permit a pre-award site survey of Building 310 and the existing demarcation facilities?

Answer: Yes. There are no physical restrictions preventing site surveys of Building 310 or the demarcation facilities. Coordination details for pre-award site visits will be provided by the Contracting Officer.

19. Please identify existing services/circuits with TSP designation and any mission-essential services requiring prioritized migration/restoration.

Answer: Circuit-specific TSP (Telecommunications Service Priority) designations are administrative details that will be coordinated with the winning provider post-award. Offerors should assume standard baseline restoration priorities during the transition.

20. Please provide the Government’s required acceptance-testing criteria, particularly for inbound/outbound calling, DID, GETS and E911.

Answer: The Government utilizes standard acceptance-testing criteria to validate inbound/outbound calling, DID routing, GETS features, and E911 functionality. The winning contractor will be expected to execute these standard checks prior to final sign-off.

21. Although diverse routing is listed as N/A, would the Government consider or desire an optional redundant/diverse solution, or should pricing strictly exclude diversity?

Answer: Diverse routing is not a baseline requirement for this effort. Pricing must be submitted based strictly on the requirements listed in the PWS.

22. As a followup to Q&A response that “POP start is firm for Oct 1 2026”, can the Government please clarify the POP start date is when contact period starts for the process of transition and cutover, and that the actual cutover / service start date is subject to vendor’s planned period needed for the cutover?

Answer: The POP start date of 1 Oct 2026 will serve as the beginning of the transition and cutover period. The actual service go-live date will be established based on the awardee's transition schedule. The Government will maintain existing services during this transition window to ensure there is no interruption to base communications.