Verizon Q and A.pdf
PDF 30 KB Posted
- Attached to
- VOIP for Norfolk and Phil areas
- Solicitation number
- N0018926RL030
About this file
This is a Questions and Answers (Q&A) document for a Verizon federal contract opportunity related to voice and telephony infrastructure services.
The government will not provide building-level endpoint data prior to award due to the scale of the requirement; offerors must base proposals on installation-level endpoint counts provided in the Performance Work Statement (PWS), with detailed building information provided post-award. Regarding encryption support, vendors are not expected to support VoSIP (a government-owned telephony network) but must remediate line degradation that prevents Secure Telephone Equipment (STE) end-to-end encryption. The government will be responsible for testing and validating existing ISP cabling, though vendors may propose repairs or replacements; the government is open to infrastructure upgrades including fiber cabling between buildings and Ethernet wiring replacement but makes no commitment to funding such proposals. Vendors should base proposals on PWS endpoint counts rather than requesting physical addresses for all locations.
Regarding 911 compliance, providing building/floor/room location data to the Government's Regional Dispatch Center satisfies Ray Baum's Act requirements for dispatchable location but does not address Kari's Law, which requires 911 dialing without any prefix. The government has no preference between on-premise and cloud-based hosting architectures. Available hosting space and power for on-premise server deployment cannot be confirmed without knowing specific location and equipment proposed, with such information to be determined during post-award site surveys. NG911 service interface specifications require government clarification beyond the dispatch routing information provided.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Solicitation Amendment N0018926RL0300001 SF 30.pdf | ||
| PWS.pdf | ||
| Small Business Coordination Record_Redacted.pdf | ||
| CAP.pdf | ||
| QASP.pdf | ||
| VOIP Phones Pricing Spreadsheet.xlsx | XLSX spreadsheet | |
| Solicitation - N0018926RL030.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
Verizon Q and A
Q1. Please provide the specific line counts per building, along with device types and quantities.
A1. As stated in previous Government responses, building-level endpoint data will not be provided prior to award due to the scale of this requirement. Offerors must base their proposals on the installation-level endpoint counts provided in the PWS. Detailed building information will be provided to the awarded offeror(s) post-award to facilitate implementation.
Q2. Clarification on whether the vendor must provide support for encryption for VoSIP or STE (V150 protocol), or strictly provide commercially available/unclassified transport connecting the VoIP or STE to an encrypted end-point.
A2. VoSIP is a government owned telephony network and vendor will not be expected to provide support. STE addressed in Question 3.
Q3. If the vendor provides only commercial/unclassified transport, is the vendor required to remediate VoSIP or STE encryption failures?
A3. A STE is a device that must be provided dial tone, however it provides it's own encryption. If there is degradation on the line that prevents successfully end-to-end encryption the vendor will be expected to remediate the line degradation.
Q4. Cabling Validation: Confirmation that if the vendor uses existing ISP cabling, we are responsible for testing/validating it, with the option to propose repairs or replacements if runs are defective.
A4. Yes. The government will consider any repair/replacement proposal, but the government is not committing to any proposal or guaranteeing any funding will be available at this time.
Q5. Infrastructure Transformation: Whether the Government is open to upgrading ISP cabling to fiber between buildings and replacing inside wiring with Ethernet alongside new IP handsets.
A5. Yes. The government will consider any proposal but the government is not committing to any proposal or guaranteeing any funding will be available at this time.
Q6. Accurate physical addresses for all locations listed in the PWS.
A6. See answer to Q1.
Q7. Routing & Dispatch: Confirmation that providing building/floor/room location data routed directly to the Government’s Regional Dispatch Center (RDC)—with the RDC handling PSAP dispatch—satisfies Kari's Law and Ray Baum’s Act requirements.
A7. The information noted will serve as "dispatchable location" information which satisfies Ray Baum Act. However, Kari Law requires 911 dialing without any prefix and is not addressed in the question.
Q8. Interface Specs: Technical and connectivity specifications for interfacing the proposed voice solution with the NG911 service.
A8. Government requires question clarification if above answer (Q7) does not suffice.
Q9. Available hosting space and power for an on-premise server deployment.
A9. Government cannot answer this question without knowing the specific location and equipment proposed. This information should be available from a post-award site survey and the government will consider any proposal but the government is not committing to any proposal or guaranteeing any funding will be available at this time.
Q10. Government preference regarding an on-premise architecture versus a cloud-based/hosted solution.
A10. Government has no preference.
File details come from the government source that posted it. Updated .