LEVIATHAN SYSTEMS

Buyer's Guide

Data Center Rack-and-Stack Services for GPU Builds: What's Included

Technical contentPublished Updated

A rack-and-stack quotation should identify the equipment's starting state, the physical change included and the evidence promised at handoff. Loose equipment may need mounting; a factory-integrated rack may need only specified site connections; installed equipment may need a named correction. Approved IT cabling, dressing, labels, physical checks and records are included only as defined in the proposal. Compare that promised result with the result you need, including any shared external connection and the party receiving the physical handoff.

Start with the equipment state and the physical result included

A useful quotation describes a change from the supplied equipment state to a defined physical handoff. Read the proposal's actual inclusions against that starting point. Mounting, included approved IT cables, dressing, labels, agreed physical checks and records can form the package; none is a universal automatic inclusion.

For loose equipment, look for the named servers or other devices to be mounted at released positions using the supplied applicable mounting inputs. Identify any included IT connections and labeling. The promised evidence should describe the installed equipment and positions, included cable and label records, agreed physical checks and remaining items at the scope's stated level of detail.

For a factory-integrated rack, identify the supplier record that describes the existing assembly and internal cabling, then isolate the site work actually offered. External connections, receiving, movement and an arrival-condition check need their own inclusion decisions. Retaining a factory record as an input neither repeats factory integration nor creates evidence of the condition after delivery.

For installed equipment needing a specified correction, identify the affected item, the approved physical change and the agreed recheck and updated record. A correction to one label or connection should not be described as a fresh installation of the whole rack. In every delivery state, the quotation should name the recipient of the physical records and carry unresolved items to their responsible owners.

Use the related rack-and-stack guide for broader readiness, elevation and workfront planning. Here the decision is narrower: does the returned offer explain the physical change and evidence being purchased, and does that cover the result you requested?

References: [L1][L2][L3][L4]

Compare named service boundaries before assuming a default

The phrase installation can include different activities in different offers. Read the applicable service description alongside the actual proposal, and have the supplier identify the selected option.

Dell's public ProDeploy description illustrates why this matters. It describes ProDeploy Infrastructure as on-site hardware and remote software installation, while ProDeploy Flex offers choices including factory configuration, rack integration and field deployment. Ask which work occurs before shipping, which remains at the customer site and which output each selected activity supplies.

Those named descriptions help interpret delivery boundaries. A catalog does not establish a particular purchaser's order, hardware eligibility or a separate contractor's entitlement to OEM-controlled work. The actual offer must identify its own selected tasks; a broad deployment label cannot supply the missing scope.

References: [D1]

Keep delivery completion separate from installation

Delivery can itself contain several boundaries. A shipment may have reached a loading dock without being in the customer's space, or reached the cage without the equipment being mounted. A rack-and-stack quotation should identify its starting location and the receiving or movement service on which it depends.

Equinix's inbound-shipment documentation provides a concrete example. It distinguishes carrier movement between the delivery vehicle and loading dock from a selected service to move packages to the customer's space. It also describes the shipment order becoming Completed after the shipment has been moved. That status concerns the documented shipment process; it does not establish installed servers, completed external cabling or a functioning cluster.

If a project coordinator reads that completion notice as installation readiness, the next team may be scheduled against the wrong starting condition. Ask what was received, where it is, which movement or unpacking activity was actually included, and which party has confirmed the next work package. Real equipment routes, handling methods and site approvals remain for the responsible qualified owners. No standard offload, lifting crew or placement method follows from the operator example.

References: [E1]

Read one complete returned offer for mixed rack deliveries

A project can contain more than one starting state. A single rack-and-stack line is especially difficult to interpret when it groups a factory-integrated rack with equipment that still needs mounting. The rack count can be correct while the physical work differs for each rack.

Fictional example EX-RS114 has two rack references. A supplier record describes RA as arriving with its devices mounted and internal connections complete. RB is an already installed empty cabinet receiving two separate servers, S1 and S2. One proposed external connection group, GX, runs between RA and RB and appears against both rack references. These are stipulated inputs for reading an offer, not observed equipment, compatibility findings or a released field plan.

The initial quotation Q1 says "two racks installed and cabled." It leaves the buyer unable to tell whether RA's existing work is being offered again, whether mounting S1 and S2 is included, or whether the shared GX is covered. The bidder returns one revised offer, Q2, with the following connected scope.

For RA, Q2 treats the supplier's factory record as a supplied input assumption. It includes no repetition of RA's internal integration and no incoming-condition inspection of RA. Its description therefore supplies no new observation or post-delivery check result for that rack.

For RB, Q2 includes two named mounting tasks: mount S1 in RB and mount S2 in RB against the supplied released position and mounting inputs. It includes the agreed equipment labels. Q2 promises an installed-position and label record for those two devices, the agreed physical-check record for that included work, and an open-item record identifying incomplete items or required owner decisions. These are promised outputs of the offer; no mounting or check has been performed in this example.

For GX, Q2 expressly excludes installation of the one shared external connection group pending an issued endpoint basis and named material-supply responsibility. Its appearance against RA and RB refers to the same group, not two independent groups. No cable quantity follows from that reference. The exclusion also means Q2 promises no installed-GX connection, label or check result.

For handoff, Q2 names the nominated customer installation lead as the recipient of RB's promised physical records and the open-item record. The handoff keeps the excluded GX and its missing inputs visible. OEM startup remains a separate package with its own responsible party; delivery of the physical records to the installation lead does not include that startup. Receipt of a file is separate from technical acceptance of the physical work.

Q2 is useful because it identifies what changes, which inputs it assumes and what evidence it promises. It is a defined partial offer for RB's mounting and records, rather than the full two-rack installed-and-cabled result implied by Q1. If the buyer needs the RA-to-RB connection, GX must still be resolved within a revised offer or in a separately defined package. Neither route is selected here. The example supplies no actual price, authorization, handling method, compatibility decision or completed result.

Separate customer-provided materials from the included task

"Customer-provided" needs an object. It could identify who supplies a cable assembly, who issues its intended endpoints or who performs its installation. A customer-supplied assembly can be the material for an installer's included task; a customer-issued drawing can be an input without assigning the customer the labor. Conversely, listing another provider's service as an input does not establish that it has been performed.

The factory-versus-site distinction needs the same care. A factory internal-cabling record describes work within its earlier boundary. It does not identify which external connections a site offer includes, and a factory test report does not supply a separate post-delivery check. Ask what physical task and record the current proposal adds to the supplied state.

In Q2, RB's supplied position and mounting inputs support a named proposed task, while GX remains expressly excluded pending its missing basis. Merely receiving the endpoint file later would not add GX to the offer or technically approve that input. The buyer still needs the applicable owner's response and a defined physical package. Keep supplied information, material responsibility and included execution distinguishable rather than treating "customer-provided" as a complete scope answer.

Ask what the checked result proves

A quoted check needs a stated output. A position record can show where equipment was installed. A cable-ID record can relate the connections in scope to the approved schedule. An instrument report has its own measured coverage and acceptance criteria. None of those outputs should be renamed full system acceptance without the responsible owner's defined requirements.

For DGX B200, NVIDIA assigns installation to its partner-network personnel or field service engineers; its first-boot page states that the designated installers also perform that setup. Use that named-system example to ask the supplier who owns the actual OEM startup package. It does not authorize a general rack-and-stack crew, prove Leviathan's OEM status or supply a bring-up procedure for another server.

Keep the quotation's physical checks separate from activities that depend on energized systems, firmware, software or workload behavior. Confirm the qualified personnel, instruments, method, report and criteria before formal optical or copper testing is promised. If system startup is outside the physical quotation, identify its owner and the handoff information it needs; do not fill the gap by adding an undocumented power-on or diagnostic task to the installation crew's work.

References: [N1][N2][L2]

Define the remaining physical package for Leviathan

Leviathan can discuss rack-and-stack, customer-supplied equipment mounting, approved cabling, routing, dressing, labeling, inspection, remediation and project-defined physical records. The equipment list, delivery state, agreed work area, approved rack positions, supplied mounting parts and requested result form the starting point for that discussion. Receiving, placement and handling need an explicit, site-specific scope rather than an assumption that a rack installation includes every movement.

Identify the appointed equipment/material supplier, approved configuration, quantities and delivery responsibilities before agreeing the physical work. Facility electrical work, structural approval and full software/system commissioning remain outside Leviathan's physical service. Power-cord connections to existing approved equipment or rack PDUs may be considered only as a separately agreed scope, subject to OEM instructions, facility authorization, personnel qualifications and insurance. Leviathan does not perform, coordinate or subcontract liquid-side work.

A request for drawings or planning outputs should identify the deliverables and reviewer. Physical layouts, routes, labels and material documentation can be discussed, with production resources, software and formats confirmed before output is promised. Preparing a BOM does not itself authorize purchasing its contents; identify the appointed purchasing owner, supplier and delivery responsibilities. An installation engagement does not establish a native CAD format, licensed engineering authority or an OEM relationship.

Send the equipment and proposed quotation boundaries together. Explain which factory or provider services are already ordered, which physical result remains, who supplies the inputs and who receives the handoff. Tell us about your project, and our team will follow up to discuss the scope, requirements and availability.

References: [L1][L2][L3][L4]

Primary sources

  1. [D1] Dell: ProDeploy Infrastructure Suite delivery optionsChecked 2026-10-16. Named ProDeploy Infrastructure and ProDeploy Flex descriptions distinguish on-site hardware, remote software, factory configuration, rack integration and field-delivery choices. Use them to question the selected delivery boundary; the actual order determines inclusion and eligibility. They do not establish Leviathan OEM entitlement.
  2. [N1] NVIDIA DGX B200: installation and configurationChecked 2026-10-16. Named product's installation-personnel requirement only; no startup/shutdown, health/stress-test procedure, duration, warranty/legal conclusion or company authorization.
  3. [N2] NVIDIA DGX B200: first-boot ownershipChecked 2026-10-16. Statement that designated personnel install this system and perform first-boot setup only. No commands, software/EULA/account setup or transfer to another OEM system.
  4. [E1] Equinix: inbound shipment and movement boundariesChecked 2026-10-16. Named operator's carrier/dock/customer-space movement and shipment-completion boundary only. No actual order, time/weight/size rule, handling method, retention policy, fees or legal liability interpretation.
  5. [L1] Leviathan: Rack-and-Stack InstallationChecked 2026-10-16. Current conditional customer-supplied physical scope and exclusions, not automatic handling, energized work, resources or compatibility approval.
  6. [L2] Leviathan: Physical-Layer Testing and Installation VerificationChecked 2026-10-16. Formal methods need confirmed equipment, qualified personnel, method, acceptance criteria and report coverage. No universal optical threshold or standard testing entitlement.
  7. [L3] Leviathan: Structured Cabling and Fiber InstallationChecked 2026-10-16. Approved customer-provided materials, routes, endpoints and project-defined records only. No cable-selection or network-design procedure.
  8. [L4] Leviathan: Integrated Physical Infrastructure InstallationChecked 2026-10-16. Combined agreed physical packages, qualified interfaces and exclusions only. Purchasing and delivery require an approved scope. No all-trades turnkey service, full commissioning or operating-readiness guarantee.

Clarify the rack-and-stack result you need

Share the equipment delivery state, included provider services and remaining physical installation. Our team will follow up to discuss scope, requirements and availability.

Discuss a ProjectEmail Project Scope