FREE DEPLOYMENT WORKSHEET

Supercomputer & AI Data Center Readiness Worksheet

Compare two locations for a supercomputer or high-density AI deployment. Identify which evidence supports each option, what still needs to be verified, and who owns the next decision.

No signup. Open the CSV in a spreadsheet and keep your facility records on your own systems.

The decision to make before you place an order

When two rooms or sites look promising, compare them against the same equipment list, load assumptions, operating configuration, and target date. A room-wide capacity summary does not tell you what the distribution serving one row can support. Make the proposed rack location the unit of comparison.

This worksheet reflects questions from the team’s experience with five independent supercomputer installations and facility-scale liquid-cooling work. Use it to organize evidence and assign next steps before the responsible project parties confirm readiness.

What to check for each location

Record the source and date of the best available evidence. Use one status for each check:

  • Documented: the relevant record exists and can be reviewed.
  • Missing: the record is missing, outdated, or not specific to this location.
  • Conflicting: the available inputs disagree or use different assumptions.

1. Equipment requirements

Are both options being judged against the same equipment and operating assumptions?

Dated supplier requirements for the rack count, load profile, cooling interfaces, weight, delivery and maintenance access.

Who to involve: Compute project lead and equipment supplier.

2. Electrical capacity

What supports the claimed capacity at the proposed rack location in the intended operating configuration?

A current record of the distribution path, recent relevant load readings, planned loads, and a capacity review by the responsible engineers.

Who to involve: Facility electrical lead.

3. Heat removal

Can the location handle the proposed air and liquid heat loads when the system is in use and when supporting equipment is maintained?

Supplier heat-load split, facility requirements and operating conditions, documented cooling allocation, and agreed responsibility for each interface.

Who to involve: Facility mechanical lead and cooling supplier.

4. Placement and cabling

Can the proposed equipment get to the location, be connected, and be serviced there?

Delivery route and layout review, floor support and service clearance records, and an interconnect and network cabling plan.

Who to involve: Installation lead and network team.

5. Installation sequence

What must be finished before delivery, installation, acceptance, or the start of operation?

Dependencies, available change windows, equipment delivery dates, milestones, acceptance responsibilities, and a plan for existing services.

Who to involve: Deployment manager and site operations.

6. Operating ownership

Who receives the alarms and maintains each facility and equipment interface after handover?

Named alarm, escalation, maintenance, and warranty owners; agreed handover records; training and response coverage.

Who to involve: Site operations lead and service providers.

Worked example: Two rows in the same facility

Illustrative only. A team is deciding where a proposed liquid-cooled cluster could go. The questions below use the same proposed system for both rows.

Electrical capacity

Row A
Missing: a room summary lists spare capacity but does not show what feeds the proposed row.
Row B
Documented: the row distribution record and a dated meter extract are available for review.

Next action: Have the electrical lead reconcile row-level evidence with the common supplier load assumptions and confirm the operating configuration.

Heat removal

Row A
Documented: the facility team has provided the cooling allocation for the location.
Row B
Conflicting: the equipment proposal uses an air/liquid split that differs from the value in the site plan.

Next action: Have the supplier and mechanical lead reconcile the expected heat loads and document what each facility system must handle.

Operating ownership

Row A
Documented: the site has a named operating owner and an escalation procedure.
Row B
Missing: the project team has not assigned a first responder for cooling interface alarms.

Next action: Assign alarm ownership and get agreement from the facility and equipment teams before handover planning.

Neither row is ready to select from this record alone. Row A needs evidence for the electrical path; Row B needs a reconciled cooling assumption and an alarm owner. A count of documented items would hide those differences.

Turn the comparison into a decision brief

  1. State the decision and date: choose a location, request another option, or hold the commitment pending evidence.
  2. Identify what would rule out each option, and list the specific evidence needed to close each open item.
  3. Name one owner and a due date for each next action. Ask the responsible project parties to record what supports the decision.

Use this worksheet to prepare a review. It does not calculate spare capacity, approve a design, or establish that a site can support a deployment.

Explore HPC & supercomputer consulting for a deployment review, a data center facility audit for an existing site, or liquid-cooling readiness advisory for the cooling interfaces.

YOUR NEXT DECISION

Let’s put clarity
to work.

Tell us what’s happening at your facility.
We’ll start with the questions that matter.

Discuss your projectU.S. engagements · International by arrangement