NETC

REQUEST FOR PROPOSAL

NETC RFP3153

This Request for Proposal seeks bids for Consortium WAN, Internet, and Equipment for New England Telehealth Consortium, a NETC member health care provider. This RFP was posted by USAC on 02/12/2025. Responses are due 5pm Eastern Time on 03/12/2025.

NETC RFP3153 – The RFP
NETC RFP3153 – The Network Plan

Please note that USAC adopts their own RFP numbering scheme and NETC’s RFP3153 is listed on the USAC site as 3153

STATUS: Bidding is closed for this RFP.

Question: There are two sections numbered 12 and 13. See, for example, Section 13.80.5 in the current RFP, which is then followed by another Section 12.1 (PDF pg. 39 of 85). Section 12.7 (same page) is then followed by another Section 13. How do you want us to number the responses given this anomaly?
Answer: We’ve updated the RFP to correct the section numbers. Please download it here.

Question: In 13.11, you request an E-LAN or equivalent. Could a Layer 3 routed private WAN be considered equivalent?
Answer: Yes.

Question: In 13.11, how do you evaluate equivalency between services and E-LAN?
Answer: Any private Multipoint-to-Multipoint service would be considered equivalent.

Question: In 13.7.1.11, what does “User and group-based policy enforcement with integration support for directory services such as Active Directory and LDAP” apply to-for example, the equipment management system, appliances, firewalls, etc.?
Answer: NETC would like to see options for appliances that integrate with directory services (Active Directory and LDAP) to enable tenant-specific (NETC Member HCP and NETC Consortium) user- and group-based policy enforcement, allowing the consortium to centrally manage WAN connections and transport overlays while each member has the option to independently use the appliance like a traditional firewall.

Question: In 13.7.1.17, what does “HTTPS proxy, various SSL/TLS protocols, and Remote Access VPN connections” apply to? Is there any specific portion of the RFP or service(s) requested?
Answer: As mentioned in the previous response, we would like NETC members to have the ability to independently use the appliance like a traditional firewall. This would include enabling services like ZTNA and Remote Access VPN.

Question: Appendix B confirmation: The list of 627 locations appears on pages 46-85 of the RFP, following Appendix A, but it isn’t labeled as “Appendix B.” Can you confirm if this is the correct Appendix B?
Answer: The RFP has been updated to include Appendix B. Please download it here.

Question: Installation Scope – Would you like us to provide a quote including installation services at all 627 locations, or do you have internal resources for self-installation at some sites?
Answer: Please provide a quote that includes installation services.

Question: Facility Type & Requirements – Can you provide additional details for each location where a Starlink bid is requested, including: . Facility type (clinic, hospital, administrative office, etc.) . Square footage of the property . Number of floors
Answer: Additional details will be discussed on a case-by-case basis during contract negotiations.

Question: Deployment Preferences – Are all locations included in the RFP expected to receive Starlink service, or are there specific sites where satellite connectivity is not required?
Answer: NETC recognizes that a single connectivity solution (including Starlink) may not be suitable for all locations. We will evaluate diverse connectivity options on a case-by-case basis to ensure each site is matched with the most appropriate and cost-effective solution.

Question: Transport Network – Is there an additional spreadsheet available that includes details on the current bandwidth and circuit type at each location? We noticed the table on page 12 lists 316 sites, while the site list on pages 46-85 includes 627.
Answer: An additional spreadsheet is not available. However, USAC’s open data includes bandwidth information for all previously requested funding and can be searched if more information is needed.

Question: In the RFP, MTU was detailed under the underlay network options (Ethernet and DIA). What is the expected MTU for the SD-WAN services providing overlay network options to end sites?
Answer: A minimum MTU size of 1500 is required.

Question: Is 366 Pinnacle Ridge Rd., Rutland, VT, a data center or health care facility? If not, why is this site included in the RFP? Are there any restrictions on power or space at this site?
Answer: This location is a POP for some Tier 1 Internet service providers and was provided as an example. Please feel free to provide pricing for each location and make note of any technical concerns in your response so that the most cost-effective solution can be determined.