Amendment 1 2025-UWMSN-00891-RFB Commercial Circuit Network Connections.pdf
PDF 302 KB Posted
- Solicitation number
- 2025-UWMSN-00891-RFB
- Issued by
- Dane County, Madison City, Wisconsin
About this file
This is Amendment #1 to a Request for Bid (RFB) issued by the University of Wisconsin-Madison for Commercial Circuit Network Connections (Event Number 2025-UWMSN-00891-RFB). The amendment responds to bidder questions submitted by January 21, 2026, at 2:00 PM and clarifies technical requirements across four primary service sections: general network circuits, circuits requiring specific diversity routing, data center interconnect DWDM circuits, and broadcast tower connectivity. The University seeks Ethernet private line point-to-point network circuits with physically diverse fiber routes from existing University fiber infrastructure, with specific routing constraints detailed for different geographic regions within Wisconsin and Illinois. Key specifications include two 10 Gbps circuits between UW-Lacrosse and UW-Platteville on the same path, 100 Gbps and 400 Gbps circuits for data center interconnect requiring LR4 transceivers (not FR4), and symmetric point-to-point Ethernet private line service rather than asymmetrical ISP or meshed configurations. The RFB submission deadline is February 27, 2026, with inquiries directed to Caleb Hall at caleb.hall@wisc.edu. Responses must be submitted electronically through https://bids.scikurt.com.
The amendment clarifies that this procurement is not E-Rate related and that the University will not adopt alternative master service agreements or state contract terms, instead expecting bidders to upload their MSA proposals for negotiation. The University confirmed that circuit endpoints are located in Wisconsin and Illinois as listed in Attachments 7 and 8, with the UW Madison data center address specified as 3135 W Highland Ave, Milwaukee, WI. The selected provider bears responsibility for data center conduit and ducts, with the University planning independent fiber tie-cable installation from its racks to meet-me rooms. Circuits in Sections 1 and 4 have no diversity requirements, while Sections 2 and 3 require specific route diversity from existing University fiber paths and primary network corridors. The University will not accept logically combined circuits as an alternative to discrete 400 Gbps service and requests that bidders propose optional pricing for circuits with optional third-path optical protection diversity where feasible.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Amendment 2 2025-UWMSN-00891-RFB Commercial Circuit Network Connections.docx | DOCX document |
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
AMENDMENT #1
COMMERCIAL CIRCUIT NETWORK CONNECTIONS
2025-UWMSN-00891-RFB
Amendment #1 serves to answer bidder questions received by 1/21/20262:00:00 PM.
# Section/Attachment Question Answer 1 General Question Is this an E-Rate request? If so, can you please provide the
470 #?
This project is not related to an E-Rate request.
2 General Question In the past, we need the customer to agree to our MSA (we can make changes and are quite flexible). We're happy to consider any additional terms that the University would like to propose and will seek to accommodate any applicable flow downs required by State law. Our MSA is attached.
Please upload your MSA in section 2.4.1 in the souring module for review/additional negotiation.
3 General Question What do you mean by protected on the individual circuits?
We understands the diversity between Group A and B circuits, but do you also want the individual circuits to be on protected paths?
We are primarily interested in unprotected circuits.
The only requirement is that if you are proposing circuits in both Group-A and Group-B, the circuits must be diverse from each other, as you mention. They do not need to be protected.
If either of your proposed circuits in Group-A and Group-B can be provisioned with optical protection with a protect path that is diverse from Group-A and Group-B (a 3rd path) then we would like to see that pricing.
4 1.1, Terms and Requirements - Purpose
Section 1.1 Purpose indicates circuit endpoints in the State of Wisconsin and Illinois, however, there doesn't seem to be an Illinois address in the RFP. Is there another address we need to consider?
All circuit endpoint locations are listed in Attachment 7 and Attachment 8. We may in the future, as for circuits in Illinois.
2025-UWMSN-00891-RFB
5 1.2, Terms and Requirements - Scope
Indicates "The University seeks commercial circuit network connections with physically diverse fiber routes from the University’s existing fiber paths…" Do we need to understand the location of University fiber paths before designing circuits?
For planning purposes and as general guidelines refer to attachment 7 and use the following information for route planning:
1) circuits in attachment 7, section 1, do not have diversity requirements.
2) In Section 2 the two circuits between UW Lacrosse and UW Platteville need to be diverse from Hwy 53 starting at Lacrosse going north via I-90 to Tomah and also should not be along I-90 between Eau Claire and Madison.
3) In Section 2, the last three circuits (UW-Superior, Marinette and UWGB) should try to avoid the path in the attached screenshot (superior-marinette-uwgb primary-path.png) which shows our approximate primary path. The farther north the route goes in Wisconsin, the better.
4) In Section 3, UW’s primary network runs from Madison to Milwaukee along I-94. Circuits should attempt to be diverse from that corridor if possible.
5) Section 4 circuits have no diversity requirements.
6 Attachment 7, section 2 – Pricing sheet
There are two separate line items for a 10Gbps circuit between UW-Lacrosse and UW-Platteville. Can we assume two separate circuits are required? Assuming so, is there a diversity requirement for these two circuits?
Two circuits (each 10Gbps) are required, so that we have 20Gbps total bandwidth between the UW Lacrosse and UW Platteville location. Both 10Gbps circuits should be on the same path. See path diversity requirements in response 5, #2.
7 6.3, Terms and Requirements - Diagram
Diagram indicates "UW Madison data center" without an address, and attachment 7, section 3 (circuits in section 6.3, Data Center Interconnect DWDM circuits) indicates Data Holdings, which is in Milwaukee. Please clarify address for UW Madison data center should be 3135 W Highland Blvd, Milwaukee, WI 53208.
The address for the UW Madison data center is 3135 W Highland Ave, Milwaukee, WI.
2025-UWMSN-00891-RFB
8 6.3.3, Terms and Requirements
Will the selected provider utilize data center conduit/ducts?
Or will selected provider be responsible for conduit/ducts?
Selected provider is responsible for conduits/ducts and may choose to check with Data Holdings on duct availability for facility entrance.
9 General Will the University be responsible for data center cross-connects (between University rack/cage and meet-me room)?
UW is planning to have their own fiber tie cables installed from their racks to both meet me rooms. We will work with the data center team for any cross-connects that are needed to our tie-cables.
10 Attachment 7 section 4 - Pricing sheet
Will the Univesity consider Asymmetrical ISP service as an alternate at the site WSUM broadcast tower (7263 County Road A, Belleville, WI)?
Asymetric ISP service will not be acceptable. We are requesting symmetric, point to point Ethernet Private Line service. NO see specs
11 6.3 Terms and Requirements – Circuit Summary
In regards to Administrative Computing: -100Gbps and Research Computing - 400Gbps Circuit Requests, will the University share with us what Applications you will be running?
No.
12 6.3, Data Center Interconnect DWDM circuits – Diagram/Summary
For the 400Gbps circuits, is it acceptable to logically combine 4x100Gbps circuits?
No.
13 6.4 - Table Header Section 6.4, Table header indicates Ethernet point-to-point circuits, however, section 1.1 Purpose, first paragraph indicates "Layer 2 Ethernet Local Area Network…". Is the requirement for point-to-point (Private Line) or Meshed (Any to Any)? Attachment 7, section 4 seems to indicate point-to-point, would appreciate clarification on the required logical configuration.
We are requesting an Ethernet private line point to point network circuit that passes all traffic transparently, including network control traffic and VLAN information.
14 RFP Event Summary Document – Close Date
Will UW consider a 4-week extension on the RFP Due Date and extend to Friday, March 27th?
No.
15 6.3.13 - Table Is 400Gbps QSFP-DD FR4 an acceptable alternative handoff for UW 400Gbps DWDM service?
No, we do not want FR4. Please propose LR4 transceivers.
16 Attachment 7, Section 3 - Pricing sheet
Column D Indicates protected and Unprotected, can we assume Groups A and B are the Protected side for Each other ? Or does both Group A and Group B each require their own Protected circuits?
UW would protect Group-A circuits with Group-B circuits (and vice versa) and our primary request is for unprotected circuits in Group-A and/or Group-B. See also the response to Question 3.
2025-UWMSN-00891-RFB
17 3054 Standard Terms and Conditions
Will UW consider using the STATE of WI Network contract Contract No. 505ENT-M23-NTWRKSRVCS 02 for T&C's for Bid Response (Where applicable)?
No.
18 General Question Would you please confirm what the address should be for the Data Center – UW Madison as referenced on the diagram? Is it the 3135 Highland address in Milwaukee?
Yes, it is 3135 Highland Ave in Milwaukee, WI.
2025-UWMSN-00891-RFB
Screenshot referenced in Section 5.
(superior-marinette-uwgb primary-path.png)
File details come from the government source that posted it. Updated .