ESBD_383214_1732307761902_[A] Technical_Response.docx
DOCX document 423 KB Posted
- Solicitation number
- 24-204
- Issued by
- Texas
About this file
This technical requirements document is part of RFP 24-204 issued by the Purchasing Solutions Alliance (PSA) of the Brazos Valley Council of Governments for Network Monitoring Services for Next Generation 9-1-1 (NG911). The document outlines comprehensive requirements for 24/7/365 network operations center (NOC) services, including network monitoring, help desk support, device configuration management, security monitoring, and Quality of Service (QoS) management for NG911 networks. The technical specifications are divided into four main sections: General Requirements (19 items), Value Added Services (6 items), Quality of Service Requirements (8 items), and System Architecture. Key requirements include monitoring of Layer 3 networks, 4G/5G LTE wireless systems, microwave links, NextGen firewalls, implementation of multi-factor authentication, and monthly performance reporting.
The document is structured as a compliance matrix where vendors must indicate whether they fully comply, partially comply, or do not comply with each requirement. Vendors are required to provide detailed explanations for each requirement in designated spaces following the compliance tables. The requirements emphasize the critical nature of QoS for 9-1-1 VoIP networks, specifically focusing on bandwidth management, network delay, jitter control, and loss prevention across both LAN and WAN environments. The document does not include pricing information, funding details, or incumbent vendor information, as it serves primarily as a technical response template for bidders.
View the file
Other files
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
RFP 24-204 Attachment A Technical Response
| Enter Vendor Name: |
This Technical Requirements attachment is comprised of a series of requirements. The Respondent is required to clearly mark one (and only one) of the three right-most columns (Complies, Does Not Comply, Partially Complies) for each requirement, as follows:
· Complies – The proposed solution does, today (or will at the time of contract award), fully satisfy the requirement.
· Does Not Comply – The proposed solution does not, today (nor will it, at the time of contract award), substantially satisfy the requirement.
· Partially Complies – The proposed solution does, today (or will, at the time of contract award), substantially (though incompletely or, perhaps, in an alternate way) satisfy the requirement.
Following the requirements is space for the Respondent to add additional information supporting, or elaborating upon, the compliance declaration for the requirements in the table. While there are no limitations on the extent of this additional information, such information should be focused on the specific requirements being addressed. Concise details and brevity are encouraged. If no additional information is being provided for a particular table of requirements, the Respondent should include a statement to that effect (e.g., “N/A,” “None,” “No details provided,” etc.) to confirm that the lack of supporting information is deliberate and not an oversight.
In this document, the following abbreviations may be used without further definition:
BOM – Bill Of Materials LAN – Local Area Network MLPS – Multiprotocol Label Switching NG911 – Next Generation 911 NGFW - NextGen Fire Walls NOC – Network Operations Center QoS - Quality of Service SNMP – Simple Network Management Protocol VoIP – Voice over Internet Protocol VPN – Virtual Private Network WAN – Wide Area Network |_| By checking this box, you acknowledge you have read and understand.
General Requirements
| Requirements: |
| Complies |
| Does Not Comply |
| Partially Complies |
| 1.1. Network Operations Center (NOC) for 24 x 7 x 365 monitoring of NG911 client network(s) – Layer 3, 4G/5G LTE wireless, microwave point to point, internet, etc. |
| |_| |
| |_| |
| |_| |
| 1.2. Provide 24 x 7 x 365 manned contact number (Help Desk). |
| |_| |
| |_| |
| |_| |
| 1.3. Notifications and escalation of repair 24 x 7 x 365. |
| |_| |
| |_| |
| |_| |
| 1.4. SNMP and ping monitoring of NG911 client network devices. |
| |_| |
| |_| |
| |_| |
| 1.5. Network router/switch configuration and management. |
| |_| |
| |_| |
| |_| |
| 1.6. Management and upkeep of circuit IDs. |
| |_| |
| |_| |
| |_| |
| 1.7. Mechanism to capture and report notification and escalation processes. |
| |_| |
| |_| |
| |_| |
| 1.8. Tier 1 escalation to NG911 client’s network provider. |
| |_| |
| |_| |
| |_| |
| 1.9. Notification to NG911 client upon resolution. |
| |_| |
| |_| |
| |_| |
| 1.10. Change management and configuration of NG911 network equipment (router/switch). |
| |_| |
| |_| |
| |_| |
| 1.11. Backup and restoration of network equipment configurations. |
| |_| |
| |_| |
| |_| |
| 1.12. Management of fault restoration of NG911 network equipment – logical and physical. |
| |_| |
| |_| |
| |_| |
| 1.13. Monitor NextGen firewalls (NGFW) and respond to incidents 24 x 7 x 365 by NOC. |
| |_| |
| |_| |
| |_| |
| 1.14. NextGen Firewall configuration support including VPN users, configuration and backup. |
| |_| |
| |_| |
| |_| |
| 1.15. NextGen firewalls (NGFW) intrusion detection |
| |_| |
| |_| |
| |_| |
| 1.16. Multi-factor authentication services |
| |_| |
| |_| |
| |_| |
| 1.17. Reports – monthly reports on availability, utilization, response time and error rates. |
| |_| |
| |_| |
| |_| |
| 1.18. Apply security patches as they become available to NG911 network devices. |
| |_| |
| |_| |
| |_| |
| 1.19. Configure traffic shaping and end to end Quality of Service (QoS) on every network element per call handling system requirements. |
| |_| |
| |_| |
| |_| |
Elaborate on each point above in the following sections.
Network Operations Center (NOC) for 24 x 7 x 365 monitoring of NG911 client network(s) – Layer 3, 4G/5G LTE wireless, microwave point to point, internet, etc.
Click or tap here to enter text.
Provide 24 x 7 x 365 manned contact number (Help Desk).
Click or tap here to enter text.
Notifications and escalation of repair 24 x 7 x 365.
Click or tap here to enter text.
SNMP and ping monitoring of NG911 client network devices.
Click or tap here to enter text.
Network router/switch configuration and management.
Click or tap here to enter text.
Management and upkeep of circuit IDs.
Click or tap here to enter text.
Mechanism to capture and report notification and escalation processes.
Click or tap here to enter text.
Tier 1 escalation to NG911 client’s network provider.
Click or tap here to enter text.
Notification to NG911 client upon resolution.
Click or tap here to enter text.
Change management and configuration of NG911 network equipment (router/switch).
Click or tap here to enter text.
Backup and restoration of network equipment configurations.
Click or tap here to enter text.
Management of fault restoration of NG911 network equipment – logical and physical.
Click or tap here to enter text.
Monitor NextGen firewalls (NGFW) and respond to incidents 24 x 7 x 365 by NOC.
Click or tap here to enter text.
NextGen Firewall configuration support including VPN users, configuration and backup.
Click or tap here to enter text.
NextGen firewalls (NGFW) intrusion detection Click or tap here to enter text.
Multi-factor authentication services Click or tap here to enter text.
Reports – monthly reports on availability, utilization, response time and error rates.
Click or tap here to enter text.
Apply security patches as they become available to NG911 network devices.
Click or tap here to enter text.
Configure traffic shaping and end to end Quality of Service (QoS) on every network element per call handling system requirements.
Click or tap here to enter text.
Value Added Services The following table lists Value-Added Services that are desired, but not required.
| Services |
| Complies |
| Does Not Comply |
| Partially Complies |
| 2.1. Development of bill of materials (BOM) for network equipment projects. |
| |_| |
| |_| |
| |_| |
| 2.2. Development of quotes for network equipment replacement projects (engineering functions). |
| |_| |
| |_| |
| |_| |
| 2.3. Development of quotes for network changes. |
| |_| |
| |_| |
| |_| |
| 2.4. Development of network diagrams. |
| |_| |
| |_| |
| |_| |
| 2.5. Development of cybersecurity policy / network management documentation. |
| |_| |
| |_| |
| |_| |
| 2.6. Other value-added services not listed above. |
| |_| |
| |_| |
| |_| |
Development of bill of materials (BOM) for network equipment projects.
Click or tap here to enter text.
Development of quotes for network equipment replacement projects (engineering functions).
Click or tap here to enter text.
Development of quotes for network changes.
Click or tap here to enter text.
Development of network diagrams.
Click or tap here to enter text.
Development of cybersecurity policy / network management documentation.
Click or tap here to enter text.
Use the space below to enter any other proposed value-added services.
Click or tap here to enter text.
Quality of Service (QoS) The importance of Quality of Service (QoS) in a 9-1-1 VoIP network cannot be overstated.
The absence of properly designed and configured QoS results in rapid deterioration of voice quality, which may be manifested in choppy or garbled voice conversations or even dropped calls.
| Requirements |
| Complies |
| Does Not Comply |
| Partially Complies |
| 3.1. QoS aims to improve performance of voice traffic over data networks by managing network bandwidth. |
| |_| |
| |_| |
| |_| |
| 3.2. QoS aims to improve performance of voice traffic over data networks by managing network delay. |
| |_| |
| |_| |
| |_| |
| 3.3. QoS aims to improve performance of voice traffic over data networks by managing network Jitter. |
| |_| |
| |_| |
| |_| |
| 3.4. QoS aims to improve performance of voice traffic over data networks by managing network Loss. |
| |_| |
| |_| |
| |_| |
| 3.5. Respondent must know the call handling system sends various types of traffic between different components such as the MDS, DDS, Consoles, IP phones and gateways. However, each category of traffic has a different requirement in terms of bandwidth, delay, jitter and loss. Respondent must be able to configure QoS. |
| |_| |
| |_| |
| |_| |
| 3.6. Respondent must know in the context of the call handling solutions, the term QoS implies end-to-end QoS between two communicating end points. It denotes the aggregate packet delay, jitter, and loss that is incurred on each IP packet by the LAN segment and WAN connection. |
| |_| |
| |_| |
| |_| |
| 3.7. Although the logical connection between both end-points portrayed in the diagram typically constitutes two or more LAN segments, the LAN’s negative impact on a packet’s QoS is, in general, minimal—due to the vast amount of bandwidth available and the non-blocking nature of the LAN switches deployed. QoS must also be implemented on the LAN to prevent it from being monopolized by unexpected bulk data transfers that might occur at inopportune times. |
| |_| |
| |_| |
| |_| |
| 3.8. A WAN, due to its bandwidth limitation, frequently poses a greater threat to voice quality between end points. When end points are connected by a “WAN cloud” (for example, IP, MPLS) that constitutes multiple intermediate nodes (for example, routers) and links with lower throughput, it is crucial that proper QoS measures are taken at every node within the cloud so that the end-to-end QoS requirement is met. To this end, a customer or VAR must ensure that a contracted service level agreement (SLA), which guarantees the network QoS, is in place with the WAN provider. It is also a good practice to assess a WAN QoS readiness by using a software tool before deploying call handling system on it. |
| |_| |
| |_| |
| |_| |
QoS aims to improve performance of voice traffic over data networks by managing network bandwidth.
Click or tap here to enter text.
QoS aims to improve performance of voice traffic over data networks by managing network delay.
Click or tap here to enter text.
QoS aims to improve performance of voice traffic over data networks by managing network Jitter.
Click or tap here to enter text.
QoS aims to improve performance of voice traffic over data networks by managing network Loss.
Click or tap here to enter text.
Respondent must know the call handling system sends various types of traffic between different components such as the MDS, DDS, Consoles, IP phones and gateways. However, each category of traffic has a different requirement in terms of bandwidth, delay, jitter and loss. Respondent must be able to configure QoS.
Click or tap here to enter text.
Respondent must know in the context of the call handling solutions, the term QoS implies end-to-end QoS between two communicating end points. It denotes the aggregate packet delay, jitter, and loss that is incurred on each IP packet by the LAN segment and WAN connection.
Click or tap here to enter text.
Although the logical connection between both end-points portrayed in the diagram typically constitutes two or more LAN segments, the LAN’s negative impact on a packet’s QoS is, in general, minimal—due to the vast amount of bandwidth available and the non-blocking nature of the LAN switches deployed. QoS must also be implemented on the LAN to prevent it from being monopolized by unexpected bulk data transfers that might occur at inopportune times.
Click or tap here to enter text.
A WAN, due to its bandwidth limitation, frequently poses a greater threat to voice quality between end points. When end points are connected by a “WAN cloud” (for example, IP, MPLS) that constitutes multiple intermediate nodes (for example, routers) and links with lower throughput, it is crucial that proper QoS measures are taken at every node within the cloud so that the end-to-end QoS requirement is met. To this end, a customer or VAR must ensure that a contracted service level agreement (SLA), which guarantees the network QoS, is in place with the WAN provider. It is also a good practice to assess a WAN QoS readiness by using a software tool before deploying call handling system on it.
Click or tap here to enter text.
System Architecture Describe your system architecture that will be used to monitor the NextGen911 networks.
Click or tap here to enter text.
RFP 24-204 Technical Response image1.jpeg
File details come from the government source that posted it. Updated .