Local and Long Distance Telecommunication Services

--------------------------------------------------------------------- Amendment #5 - Final follow up questions submitted for clarification. Q11 follow-up - If we feel we can establish service in under 180 days, will the Government accept delivery sooner than 3/29/26? A11 follow-up - Absolutely, the government will accept delivery sooner. Q12 follow-up - In accordance with industry standards, we have diversity within our cloud SIP product. To clarify our original question- would the customer like more than one physical transport circuit to their location, and would those two circuits need to be physically diverse with regards to their route taken and entrance into the building? Essentially- do you require a primary and a backup circuit in case the first one goes down? A12 follow-up - Yes, more than one physical transport circuit is needed and they need to be physically diverse. We require a primary and a backup circuit. ------------------------------------------------------------------------------------------------ Amendment #4 - Additional question in regards to the solicitation. Q12. The SAM posting Technical/Installation and Cutover Approach requires offerors to address link diversity. PWS Section 3.8 provides a description of what diversity is but there are no details within the PWS regarding a diversity requirement for this contract. Is there a diversity requirement? If so, what level/type of diversity does the Government require? A12. �Currently, we have two TDM circuits that provide Local/long distance service. The PRI's connect to two different voice gateways. If the plan is to connect to ethernet we could reconfigure one of the Cisco 4451 gateways to support a couple ethernet connections�. ------------------------------------------------------------------------------------------------------------------------------------- Amendment #3 - Due to the difficulty in opening attachments causing the delay in receiving questions from vendors, the Submission of Offers is extended to 22 Sept 2025 at 3:00 pm. Additionally, the Submission of Offers only requires three parts - Administrative, Technical and Price. Past Performance is NOT required. Only the Technical and Price shall be evaluated for decision of award. Questions Submitted Q1. We request an extension to the quote due date by two weeks from the release of questions & answers to provide sufficient time for offerors to provide a complete, compelling, and compliant offer. A1. Extention will be given till 22 Sept 2025 at 3:00pm to allow for evaluation and award before the end of the fiscal year. Q2. In addition to an extension to allow time to respond to Q&A, we request additional time to respond to the solicitation due to short timeline and offerors' inability to access the solicitation documents prior to 09/08/2025. A2. Unfortunately due to the time constraint of the end of the fiscal year, any further extention could prevent evaluation and award prior to 30 Sept 2025. Extention will be given till 22 Sept 2025 at 3:00pm. Q3. Is there an incumbent contractor, and if so, who? A3. AT&T currently provides the service. Q4. Is there any historical usage for this account in terms of total LTS minutes/month? A4. None Q5. How many concurrent call paths are required? A5. This is unknown at this time. Q6. What is the average number of monthly long-distance minutes? A6. This is unknown at this time. Q7. Is international long-distance calling authorized? If so, to what countries and what is the average number of international monthly long-distance minutes? A7. This is unknown at this time. We have to have capabilities to call all countries, but the minutes are determined by mission which is unknown. Q8. Does the Government's PBX send out one static number for CallerID on 911 calls, or is it the Government's intention to send a unique DID depending on the device that the 911 call was placed from? A8. We have our own internal 911, then our Security Forces will call the civilian 911 when needed. We don't have a preference on what number is displayed. Q9. Appendix 1 PWS shows 2 existing PRIs, however Objective 1.2 is only asking for 24 concurrent calls. Please confirm that 24 concurrent calls is what the contractor is to provide. A9. Confirmed, 24 concurrent calls is needed. Q10. The SAM posting states "The response shall consist of four parts: Administrative, Technical, Price, and Past Performance." There are no instructions for Past Performance submissions. Please confirm that offerors are not required to submit Past Performance information. A10. Changes have been made with this amendment, the only parts required on the offer will be Technical and Price. Past Performance and Administrative are not required. Q11. While the SAM posting states that the projected Start of Work is 30 September 30, 2025, Section 3.1.1 states that "Installation, circuit assignments, all possible/applicable testing, records� management, cut over and Government acceptance shall be completed NLT one hundred and eighty (180) days after contract award for Pittsburgh ARS, PA." For proposal purposes, should we use the PWS statement as the guide for the Installation and Cutover Plans? A11. Yes, the anticipated start date for the contract is 30 Sept. Plans should start at 30 Sept and work out to the 180 day mark stated in the PWS, which should be March 29, 2026. __________________________________________________________________________ Amendment#2 - There was an issue with opening the original "Attachment 2 - Price Schedule" ; new excel file has been added __________________________________________________________________________ Amendment#1 - There was an issue with opening the original PWS (pdf); a new pdf attachment has been added __________________________________________________________________________ This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in FAR Subpart 12.6, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; Offers are being requested and a written solicitation (paper copy) will not be issued. Further, Offerors are responsible for monitoring this site for the release of amendments (if any) or other information pertaining to this solicitation. Solicitation FA671225Q0010 is issued as a request for quote (RFQ). This solicitation document and incorporated provisions and clauses for commercial items are those in effect through Federal Acquisition Circular (FAC) 2025-05, Electronic Code of Federal Regulation (eCFR) https://gov.ecfr.io/cgi-bin/ECFRl, Defense Federal Acquisition Regulation Supplement Publication Notice (DPN) 20250825 and Department of the Air Force Federal Acquisition Circular (DAFAC) 20241016. It is the Offeror�s responsibility to be familiar with applicable provisions and clauses. See https://gov.ecfr.io and https://www.acquisition.gov for the full text of all provisions and clauses incorporated by reference herein. Class deviations can be found at https://www.acq.osd.mil/dpap/dars/class_deviations.html This procurement is being issued as a 100% Total Small Business Set Aside, under NAICS code 517111, Wired Telecommunications Carriers, and a small business size standard of 1,500 employees. The Contractor shall provide all labor, tools, facilities, materials, and services needed to perform and provide loc