2025-UWMSN-00894-RFP Amendment 1 - Data Center Colocation Services.docx

DOCX document 2 MB Posted

Attached to
DATA CENTER COLOCATION SERVICES (2025-UWMSN-00894-RFP)
Solicitation number
2025-UWMSN-00894-RFP
Issued by
Dane County, Madison City, Wisconsin

About this file

This document is an Amendment #1 to a Request for Proposal (RFP) for Data Center Colocation Services issued by the University of Wisconsin-Madison, identified by event number 2025-UWMSN-00894-RFP. The amendment addresses bidder questions and extends the proposal due date to June 9, 2025. The university seeks a data center colocation service within 150 miles of Madison, Wisconsin, with an initial requirement of 500kW power capacity, expanding to 1.5-2MW within two years. The project anticipates a phased migration beginning in late summer/early fall 2026, with a steady deployment over 1.5-2 years. The ideal facility should support 10-25kW rack density initially, with potential for higher-density racks up to 50kW, potentially requiring liquid cooling solutions.

The procurement allows for both bundled and unbundled power pricing models and seeks providers with robust infrastructure capabilities. The university prefers contiguous space, initially anticipating 80-100 30-inch wide racks within the first two years, with potential secure storage requirements around 50-100 square feet. Specific technical requirements include support for research computing equipment, load ratings of 2500-3000 lbs per square foot, and flexibility for future technological needs. The university will lead migration efforts and does not require migration planning assistance from the vendor. Proposers must submit through the online platform at https://bids.sciquest.com/apps/Router/PublicEvent?CustomerOrg=UWisconsin, with all questions directed to Caleb Hall at caleb.hall@wisc.edu.

View the file

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 Data Center Colocation Services

2025-UWMSN-00894-RFP

Amendment 1 is issued to answer questions from bidders and extend the due date to June 9, 2025.

Number
Question
Answer
1.
The Word document references 25kW per rack, while the Excel sheet lists 35kW per rack—can you confirm the correct requirement?
The scenario in the Excel spreadsheet is hypothetical and does not represent an articulation of specific requirements. It is a costing exercise for respondents to use as a baseline and allows us to compare costs more easily. The Word document is the list of actual requirements.

10-25kW rack density is listed as a mandatory requirement in 3.1.4. However, we would like to know how you would accommodate higher-density racks as per 3.8.16. It’s likely a rack up to 50kW would benefit from liquid cooling.

2.
What is the anticipated award date for this project?
Specific dates are not known at this time; however, we anticipate awarding near the end of calendar year 2025.
3.
Do you have a target move-in date identified?
Specific dates are not known currently; however, we anticipate pre-go-live work to occupy the first 6 months of 2026 and move in to begin sometime in late Summer/Early Fall 2026.

Move-in dates depend on availability of suitable fiber paths and service provider site enhancements that may be required.

4.
Is liquid cooling needed immediately, or is there a projected date when it becomes required?
We anticipate liquid cooling will be needed anywhere from immediately to within 6 months of move-in (see answer #3).

We will entertain a solution provided by the service provider or a solution brought by UW that can be plumbed into existing infrastructure.

5.
Can you provide visibility into the ramp schedule (expected timeline for load deployment)?

Once we can take occupancy (post network and facility work commissioning) we begin migration from existing facilities immediately. It will not happen as a bulk move or rapid deployment from existing facilities but will be a steady flow for about 1.5-2 years.

We need to ensure that .5MW power capacity is available immediately (post network and facility work) with a plan to grow up to 1.5-2MW within 2 years.

6.
The Excel sheet shows 400kW total, but the request is for 500kW—can you confirm which figure we should reserve immediately?

See answer #1. The requirements are in the Word document and the 500kW is the amount we want available immediately.

7.
Are there any specific carrier requirements (e.g., BadgerNet or others)?

UW has specific transport (circuit) specifications as identified in the RFP though we do not have specific requirements regarding mandatory carrier(s).

8.
Section 3.8.4 – One Line Diagram: WE are happy to provide but would need an NDA in place. Is that something we can arrange?

No.

Any information contained in the Proposer’s response that is proprietary must be detailed separately on form DOA-3027. Marking of the entire response as proprietary will neither be accepted nor honored. The University cannot guarantee that all such material noted remains confidential, particularly if it becomes a significant consideration in contract award. Information will only be kept confidential to the extent allowed by State of Wisconsin Public Disclosure Law (refer to Standard Terms and Conditions, Section 27.0).

This form is available in the sourcing module Supplier Acknowledgements/Certifications section 2.1.5, complete and upload it with your response.

9.
Could you please clarify whether "immediately available" refers to power capacity that is currently online, or power capacity available upon contract execution? Additionally, do you have a target date for contract execution or for the deployment to be operational?

Available upon contract execution. See answers #2 and #3.

10.
The proposal specifies that the data center must have .5MW total capacity immediately available, with 1.5–2MW available within 2 years, and it must be no further than 150 miles driving distance from 432 E Campus Mall in Madison, WI.

Correct.

11.
(Intentionally left Blank)
(Intentionally left Blank)
12.
Our facility is a SOC2 facility with 4.5 megawatts. With our facility out of state does this eliminate us from submitting?
Not if you are within the 150mi driving distance limit.
13.
We have submitted for this same RFP

(2025-uwmsn-00894-RFP) a few months ago. Should we re-submit?

25-102824-RFI Request for Information was issued solely for information and planning purposes for a future Request for Proposal. It did not constitute a solicitation, and no award/contract would result from the RFI.

Regardless of whether you responded to the RFI, to be considered for RFP 2025-UWMSN-00894-RFP, please register with Shop@UW and respond to the RFP.

14.
Our potential response would require large capital investment for expansion to existing DC's within the 150 mile requirement. We could avoid this large capital investment if UW were willing to waive the 150 mile distance from campus requirement. Will UW be willing to firmly waive this requirement up front? This RFP response is intensive and laborious and as such, without this firm requirement waiver up front, we likely cannot invest the time into the response.
We cannot waive this requirement.
15.
Our potential response would require a build out to support water cooled racks in a DC within 150 miles. Based on this, we would like to know: When does the environment need to be ready?

See answer #4.

16.
Would the University be willing to grant a two-week extension?

The University will extend one week, to June 9, 2025.

17.
Do you have any private storage or office space required? (Not to send, but to add to response)

The RFP does include requirements for secure storage and questions related to the availability of conference rooms and office space.

See 3.6.2, 3.6.4, 3.3.8

18.
Is being a member of the CQE (Chicago Quantum Exchange) a benefit to the University?
Not relevant to this RFP.
19.
Do you have an estimate of the number of cabinets and any details around the size of the cabinets (i.e.; 24” or 31.5” wide and 42 or 48” depth)?

See answer #47. The quantity of racks will grow with time, to answer this question requires more detail about when the sample is taken (initial 6 months, 1 year in, 3 years in, etc.) We currently prefer 30" wide (31.5), 48" deep, 45 RU tall racks.

Number of cabinets depends on power density levels supported by the provider.

20.
For the Network - Can individual Ethernet circuits be aggregated on larger capacity channels, i.e. 800G or 1.6T?
Yes, smaller circuits can be aggregated on larger photonic waves but diversity between Group-A and Group-B circuits must be on different photonic waves and different equipment on geographically diverse (separate) paths.
21.
Is there any flexibility to the 150 miles? If the data center is outside the 150 miles should the responder with draw and not submit a response?

The 150 mile driving distance requirement is mandatory.

22.
The 30 day cancellation for convenience, is that negotiable? Is the University agreeable to penalties for early cancellation?

See section 2.1 Supplier Acknowledgements/Certifications.

Question 2.1.3. allows proposers to provide modifications to the terms and conditions. They must be mutually agreed upon.

23.
When is decision expected to be made?

See answer #2

24.
When is UW looking to have access to the facility?

See answer #3

25.
10 racks at 15kW and 5 racks at 35kW is 325kW. Would the actual commit for the first phase be 325kW?

See answer #1

26.
When would space need to be available?

See answer #3

27.
When do you plan to award the business?

See answer #2

28.
What is the timeline to begin the deployment?

See answer #3

29.
Although the requirements state 150 miles does the proposed facility need to be in the state of Wisconsin?

No

30.
Please confirm that Phase 2 will be conducted only after the down-select of the highest scoring Phase 1 Proposers and the current response should not address the Wide Area Network Feasibility Analysis

Correct.

31.
Will the University lead the migration program to include the identification of affinity systems for migration groups, identification of systems to migrate in a single event and the scheduling and change control for those moves? This is to confirm that the requirements focus on ‘Day Of” activities rather than program management for the full migration which are also available if required by the University

The UW will lead all aspects of the migration efforts. At this time we do not anticipate needing migration planning assistance from the vendor.

We would entertain use of a Data Center Infrastructure Management system if available. See 3.10.5

32.
We are a full stack service provider and can offer Remote Hands support across every technical discipline from the hardware configurations through application, middleware and database support. Please describe the anticipated scope of remote hands needed by the University so that we can identify the appropriate labor rate for project services

We are looking for remote hands only for physical hardware support.

33.
Do any existing racks currently require 6 whips and if so, how may racks are currently exceeding 22kW per rack

We are currently not running any racks at this level but that is due to constraints at our existing facility. We anticipate needing these capacities, however, to support higher density installations.

34.
Do all existing racks have redundant PDUs
No. Per 3.1.4-3.1.5, approximately half of our workloads require power redundancy, and half do not require redundancy.
35.
To aid in the design of the power distribution, please provide rack PDU specifications currently in use such as redundant L6-30 208V 30-amp service or similar 60-amp service to support high density racks.

Generally we use a combination of AP8865's and APDU10452ME(MO) in 20/30/60 configurations as needed.

See #33, 34, #1.

36.
When describing contiguous growth for new customers, should the proposer anticipate a single cage or new cages for each new customer as this influences the original design if a single cage is required to support all growth

UW equipment may colocate within a room or cage with other customers. We may have a need for a dedicated cage in order to comply with specific regulatory requirements in the future, however in general UW equipment does not require its own cage.

We do expect UW equipment to be fully segregated into its own racks, not commingled with non-UW customers within the same rack, and the racks be contiguous as much as possible for networking simplicity.

37.
What is the current liquid cooling solution in use today?
None in use currently due to constraints in our current facility. We have several research groups that will require liquid cooled hardware within the next year. We do not know what systems those will be at this time.
38.
Can the University provide a count of the number of existing racks and/or the currently consumed floor space

See answers #47 and 51

39.
Is the increase in power attributed to projected growth or does this timeline anticipate a multi-year process to migrate to the new DR solution

The increase in power is a combination of migration from existing facilities and growth.

40.
The RFP describes a ramp from .5MW to 1.5-2MW within 2 years. What is the current power consumption of the existing DR environment

We are not running a Disaster Recovery (DR) environment, we generally configure High Availability (HA) systems across multiple on and off-campus facilities, the ramp-up projections are a combination of migration from existing facilities and growth.

The research computation workloads deployed as higher-density racks will not have a DR site.

41.
Are optional services like migration support or consulting scored or just informative?

If the services are identified in a requirement question, then they will be scored. You may also list any related optional services you offer.

42.
Is there any documentation not explicitly listed in the RFP that UW expects (e.g., one-line electrical diagrams, full cabinet specs, site photos)?

See 3.8.4 and 3.8.12 in the RFP. UW may seek clarifying information throughout the evaluation process.

43.
For facilities built to Tier III or Tier IV equivalency but not formally certified by Uptime Institute, how will UW evaluate equivalency claims across power, cooling, and network systems? Will documentation demonstrating functional equivalency be considered equal for scoring purposes?

See 3.3.2. The University will be the sole judge of equivalent acceptability. We would expect SLAs and / or other supporting documentation to demonstrate the proposer’s self-attestation.

44.
If our pricing model supports both bundled and unbundled power rates, should we submit both pricing options or select only one format in the Cost Proposal Form?

Both please.

45.
Can UW confirm whether the required 0.5MW of immediately available power must be delivered from a single contiguous block of space, or can it be distributed across multiple pods or suites within the facility?

We prefer contiguity as it simplifies our in room networking deployment and saves us money in that regard.

However, if there are different spaces serving different purposes, for example a dedicated room for liquid cooling solutions or higher-density racks, we may split our deployment across multiple spaces.

46.
Does the university need connectivity to cloud service providers, WiscNet or Internet2?

Network interconnect connectivity to Cloud service providers, WiscNet and Internet2 is not needed or required. However, WiscNet may provide transport (circuit) services that meet specifications identified in the RFP. UW will provide our own cloud, Internet2 and WiscNet network interconnection services.

47.
Regarding contiguous space, how much does UW-Madison expect to reserve for future growth? (How many 30" wide cabinets?)

The exact number is not known at this time and would be negotiated. We could roughly anticipate about 80-100 30” racks within the first 2 years.

Number of cabinets depends on power density levels supported by the provider.

48.
What specific load rating thresholds are required for equipment support in the white space areas? Are there any unique requirements for heavier research computing equipment?
Prefer a minimum of 2500lbs psf but prefer 3000lbs psf or above for high density loads.
49.
Is the university seeking flat rate or metered pricing?

We want to see both options represented.

50.
Are proposers allowed to modify component sections to align with their company's specific terminology and billing methodology?

As long as a crosswalk table or some other key is present to help us understand what you translated into your local parlance.

51.
What is Raw Floorspace Reservation and how much is needed?

The initial floorspace reservation would likely be in the 600-900 sqft range but exact numbers are not known at this time.

See #47.

52.
How much secure storage is required?

Likely L10ft x D5ft x H10ft or larger.

53.
Is the 100 hours of remote hands and 50 hours of smart hands the total estimate for the entire term of the contract, or is it just for the first year?
For the purposes of the hypothetical costing scenario, those are per month numbers.
54.
Besides racks and PDUs, what else is the University considering bringing?

In-room networking, in-rack liquid cooling solutions possibly, stand-alone rack systems, other networking as described in the RFP Phase 2 section.

55.
Is the University considering the need for dedicated office and storage space? Is there a specific area required? (How much?)

See answer #17

We are scoring based on dedicated secure storage ability, and are interested in what other amenities are available such as conference rooms, office space, etc.

56.
What type of liquid cooling is required?

Exact configurations are not known at this time but we are considering Liquid to Air rack-based direct liquid cooling (DLC) and variations on that theme. We are just getting our first requests from researchers and will need to work with them to understand specifics.

57.
Can the University provide a preliminary power ramp schedule?

We expect to be at 500kW within the first year and a half to 2 years but an exact power ramp schedule is unknown at this time and is highly determined by migration pacing and new growth requests.

58.
Can the University provide a preliminary project schedule, including move, migration, and ready-for-service dates?

See answers #2 & 3

59.
Can UW Madison provide an estimated contract start date?

Can UW Madison provide an estimated contract award date?

See answers #2 & 3

60.
Please detail expected timelines for proposal selection, vendor down selection, site tours, contract award, and contract commencement.

See answers #2 & 3, we expect to request any site tours within approximately 3 months of the RFP due date. Timing of all steps depends on the number of responses and other factors.

61.
is this bid considered a small business set-aside? WOSB set-aside?
See Section 1.11 Supplier Diversity Preference section of the RFP.

File details come from the government source that posted it. Updated .