---
title: "Partial GPU Deliveries: Install in Phases or Wait for the Complete Kit?"
description: "Leviathan Systems — Technical content Published 2026-10-20; updated 2026-10-20."
canonical: "https://www.leviathansystems.co/articles/partial-gpu-deliveries-install-in-phases-or-wait"
last-updated: "2026-10-20"
---

# Partial GPU Deliveries: Install in Phases or Wait for the Complete Kit?

Leviathan Systems — Technical content
Published 2026-10-20; updated 2026-10-20.

Phase an installation when an identifiable package has its required materials and permissions, produces a useful handoff, and justifies the additional attendance and coordination it creates. Wait when the proposed early visit would mainly expose unfinished work, repeat setup or leave a dependency unchanged. Compare whole-project, rack-by-rack and task-by-task proposals against the same remaining scope before committing a field window.

## Find the smallest package that is useful to complete

A project can have most of its purchase value onsite and still lack the inexpensive item that prevents the next installation task. Start with the result the buyer needs from an early visit: equipment mounted in an identified rack, one rack’s agreed connections completed, or a defined physical package handed to the next team. Then identify the materials, applicable instructions, access and decisions that result depends on. A delivery percentage is a poor substitute for those relationships.

The supply boundary can explain an apparent mismatch. NVIDIA’s DGX B200 introduction says network cables and adaptors are not shipped with that system. The server’s arrival therefore cannot establish that its separately supplied network package is available. This is one named product example, not a statement about another OEM’s shipment or the contents of the customer’s order. Confirm the actual order and installation package with the appointed suppliers.

A useful partial package has an endpoint. The receiving party should be able to identify what was completed, which source issue it used and which downstream decisions remain. If the early task ends with equipment awaiting another party’s work, agree who holds the equipment and records in that state. Receipt, storage, custody, protection and later access need their actual arrangements; an installation visit does not automatically provide them. The existing receiving and customer-furnished-material guides cover those underlying records. Here the decision is whether an early installation package is worth purchasing.

References: [N1](https://docs.nvidia.com/dgx/dgxb200-user-guide/introduction-to-dgxb200.html)

## Compare three release options against the same scope

Whole-project release waits until the dependencies for the agreed combined package are available. It can consolidate the proposed attendance, but the buyer carries the wait for the last relevant dependency. It still needs a real field estimate: one proposed visit is not evidence that all remaining work fits within its access window.

Rack-by-rack release groups the included mounting, connection and records for one rack before moving that rack into its defined handoff. This can produce an earlier usable physical package when the racks are genuinely separable. Shared connections, common access and a receiving reviewer can still join the packages. A local rack handoff should identify those open interfaces rather than describe the whole cluster as complete.

Task-by-task release can use an early window for a bounded activity across several racks, followed by later connection or verification packages. That approach creates more interim states to manage. Ask whether the first activity would need to be repeated or disturbed by a later design, access or material change. Its value is strongest when it removes a real predecessor for a later team and its result can be preserved and accepted within the agreed scope.

Compare those options using one included equipment and connection list. Otherwise an early proposal may look faster because it leaves more work for someone else. Keep OEM-controlled installation and startup, facility work, formal testing and network or software acceptance with their actual authorized owners. Phasing the physical contract does not redistribute their authority.

## Work the delivery calendar before buying an early visit

Consider a wholly fictional two-rack project. At day 0, the proposed mounting packages for racks A and B have their identified servers and mounting kits. Separate network-material packages are expected and, for this illustration, assumed available for A on day 5 and B on day 11. Candidate site windows are days 2, 7 and 12. Assume all other prerequisites for the included tasks have been resolved by their responsible owners. These are planning stipulations, not a supplier forecast, production rate or permission to perform work.

The buyer requests three alternatives against the same final physical scope. A consolidated proposal considers day 12 for the combined package. A rack-by-rack proposal considers A at day 7 and B at day 12. A task-by-task proposal considers mounting at day 2, A’s connection package at day 7 and B’s at day 12. The table counts proposed attendance dates only. It supplies no task durations, staffing, test outcome or promise that any scope finishes in one window.

Under these assumptions, the day-2 proposal cannot make B’s missing network material available before day 11. It may remove mounting work from a later visit, but that benefit depends on the actual remaining-work estimate and whether the mounted arrangement can be retained. If the buyer’s urgent milestone is A’s physical handoff, the rack-by-rack alternative deserves a separate estimate. If the milestone requires both racks and their shared interface, an early partial visit may leave its driving dependency unchanged.

This is the useful scheduling question: which later activity becomes available because of the early package? GAO’s Schedule Assessment Guide explains why a reliable schedule models the activities leading to a milestone and helps assess the effect of change. Apply that principle to the actual project dependencies. Calendar activity alone is insufficient evidence of progress toward the purchased result.

References: [G1](https://www.gao.gov/products/gao-16-89g)

Fictional comparison: three attendance proposals for the same two-rack physical scope
| Proposal | Candidate dates and package basis | Question to resolve before commitment | Source |
| --- | --- | --- | --- |
| Whole project | Day 12: consider the combined A and B package | Can the estimated work, resources and required reviews fit the actual window, and is waiting acceptable? | Planning analysis |
| Rack by rack | Day 7: consider A; day 12: consider B | Is each rack package useful and separately releasable, including any shared connections and receiving review? | Planning analysis |
| Task by task | Day 2: consider mounting; day 7: A connections; day 12: B connections | Does early mounting remove later work without creating unowned interim states, repeated setup or foreseeable rework? | Planning analysis |
One project, two rack references and three alternative proposals with one, two or three candidate attendance dates. No actual work, duration, crew, completed rack, installation method or delivery commitment is represented.

## Price the attendance and the open interface

Ask the installation provider to distinguish the remaining task effort from the costs and conditions associated with attendance. An alternative can contain the same mounting and cabling tasks while requiring different travel, site induction, access, setup, supervision or review arrangements. Those items may be charged in different ways under the actual proposal. This article supplies no market rate, minimum callout or standard charging rule.

Compare what happens if the material date moves again. Which dates are merely requested, which are confirmed, and what process changes them? How does the proposal treat a blocked workfront, a cancellation, an additional attendance or a change to already completed work? Have the responsible commercial parties explain the actual terms. A useful scope comparison identifies the exposure; it does not invent a contract remedy or assume that an installer absorbs it.

Also identify who supports the interval between visits. A partial installation may leave equipment, spare materials, incomplete connections or records awaiting another party. The buyer needs the actual storage or custody arrangement, access owner and next handoff. An earlier mounting date can transfer a dependency into this interval rather than remove it. Conversely, waiting can leave received equipment at a location with its own movement and storage conditions. Evaluate both sides using the facility’s real arrangements.

The case for an early visit should state the benefit being purchased: a defined package ready for another authorized team, an earlier separately accepted physical handoff, or a verified reduction in later work. Then compare that benefit with the quoted additional attendance and coordination exposure. More visits and fewer visits can each be reasonable; neither is a universal lower-cost choice.

## Use a task-release decision instead of a carrier status

A shipment update answers a logistics question. An installation release answers whether the specified task can proceed under its actual scope. Keep the supply owner’s delivery forecast, the receiving record and the installation provider’s confirmed package connected, while retaining what each establishes.

Equinix’s inbound-shipment documentation provides a concrete operator example. It tracks received packages and describes its shipment order reaching Completed after movement from the loading dock. That status does not establish that a rack was installed or that every separately ordered material line is available. The actual site’s process controls; the example is not a receiving rule for another operator or a service included in Leviathan’s installation offer.

Before confirming a partial package, return the exact material allocation, current source issue, permitted work area, available window, responsible performing party and agreed output to its release owner. Ask the provider to identify any remaining assumption that could prevent the proposed visit from producing that output. If the answer is still dependent on an unconfirmed delivery, retain the uncertainty explicitly rather than converting an estimated arrival into confirmed attendance.

A supplier-proposed alternate is a separate technical and commercial decision. The appointed design or OEM authority must resolve applicability, and the purchasing owner must resolve the order. A desire to use an early window does not approve the substitute. Similarly, a completed early task remains tied to the configuration it used; a later equipment or endpoint change can require an affected-scope review.

References: [E1](https://docs.equinix.com/smart-hands/shipping-receiving/sh-inbound-shipments/)

## Request comparable phased-installation proposals

Send the equipment and rack list, the separately ordered material lines, their actual received and forecast states, current layouts and endpoint sources, available site windows and the physical milestone you need. Identify which factory, OEM or facility packages are already ordered and which work remains for the installation provider. Ask for the whole-project, rack-by-rack or task-by-task alternatives that are genuinely relevant, rather than requesting three quotations by default.

For each proposed phase, request its included work, prerequisites, estimated effort and window, attendance assumptions, output, receiving owner and treatment of the remaining interface. Keep physical mounting or cable records distinct from formal test results, system startup and operational acceptance. Those separately scoped tasks require their actual personnel, equipment, method and accepting authorities.

Leviathan can discuss the agreed rack-and-stack, physical cabling and documentation package, including how proposed workfronts depend on customer and supplier inputs. Receiving, freight, storage, OEM installation authority and other specialist resources require explicit confirmation; no owned facility, inventory, permanent crew or delivery guarantee is implied. Identify the appointed supplier and purchasing owner. A material list or an installation discussion does not create a procurement or resale commitment.

The useful inquiry is specific: which partial physical result matters, what is actually available to support it, and what would justify another attendance? That gives the team a decision it can assess against the real scope instead of a request to send people because some equipment has arrived.

## Primary sources

- [N1 — NVIDIA DGX B200 User Guide — separately supplied network cables and adaptors](https://docs.nvidia.com/dgx/dgxb200-user-guide/introduction-to-dgxb200.html). Checked 2026-10-20. Named system’s network-material shipment boundary only. No actual customer order completeness, approved alternate, installation authority, availability or company supplying capability inferred.
- [G1 — U.S. GAO — Schedule Assessment Guide, GAO-16-89G, December 2015](https://www.gao.gov/products/gao-16-89g). Checked 2026-10-20. Official publication overview: reliable schedules model activities leading to milestones and help analyze change and schedule/cost effects. No government rule adopted for the customer, installation productivity, crew estimate or actual critical-path calculation supplied.
- [E1 — Equinix — Inbound Shipments to an IBX](https://docs.equinix.com/smart-hands/shipping-receiving/sh-inbound-shipments/). Checked 2026-10-20. Provider-specific received-package tracking and shipment-order completion after movement only. No storage deadline, handling procedure, universal operator policy, logistics offer or actual customer shipment finding adopted.

## Related Leviathan resources

- [Receiving and staging: understand the actual shipment handoff](/articles/receiving-staging-gpu-equipment)
- [Customer-furnished materials: reconcile task allocation and shortages](/articles/customer-furnished-materials-installation-checklist)
- [Deployment timelines: model the finish-driving dependencies](/articles/gpu-deployment-timeline)
- [Rack-and-stack installation scope](/services/rack-and-stack)
- [Turnkey deployment coordination scope](/services/turnkey-gpu-deployment)

## Compare the physical installation packages

Share the equipment, material delivery states, site windows and the partial or complete physical result you need. Our team will follow up to discuss scope, requirements and availability.

[Discuss the scope](/contact?service=rack-and-stack&from=/articles/partial-gpu-deliveries-install-in-phases-or-wait)