LEVIATHAN SYSTEMS

Installation

Receiving and Staging GPU Equipment: A Custody Checklist

Technical contentPublished Updated

Plan receiving as a transfer of equipment, condition information and responsibility. Before booking a delivery, identify who can accept it, who may open the packaging, where exceptions are held and which approved instructions govern the next movement.

Agree the receiving boundary before the truck arrives

Name the delivery coordinator, facility receiving contact, customer asset owner and installation lead. One person may hold several roles, but each decision needs an identified owner. Confirm the delivery reference, permitted arrival window, location, storage arrangement and the person who can resolve a discrepancy. A delivery appointment does not establish that the installation team has accepted custody.

Facility arrangements differ. Equinix publishes a specific inbound-shipment process; use it as evidence that receiving is an operator-controlled activity, not as a rule for every data center. Obtain the actual destination instructions and share only the shipment details needed by authorized recipients.

References: [E2]

Keep the Purchase Delivery Term Separate from the Site Receipt

A freight-inclusive quotation can name the site without supplying the same answer as a commercial delivery-point return. Ask the appointed commercial owner to identify the applicable term, edition, agreed point and source reference. Keep that return alongside the site receipt rather than treating the word delivered as one status that closes every question.

In his personal Introduction to the Incoterms® 2020 Rules, Charles Debattista distinguishes a C-rule's paid carriage destination from its delivery point. His explanation also separates the sale terms from other agreements and flags variations and multi-carrier questions. The author's views are not the Rules themselves. Use that explanation to identify a missing commercial input, not to choose a trade term or decide what a real agreement does. [ICC-I2020]

RCV-TERM-31 is an original fictional comparison. Quote Q31 names invented Site D as the carriage destination under a stipulated CPT basis citing the Incoterms® 2020 Rules. A separate response, CR31, from the appointed commercial owner identifies invented P as the agreed delivery point and cites the fictional agreement reference. Stipulate that return for this example; do not derive P from the three-letter label, assume a first-carrier default or substitute the site address for it. D and P are different labels, not actual locations, and no transaction or physical work is described.

Later, receiving return RR31 records two package references at D, with external identifiers recorded but one underlying order line still unreconciled. Custody return CU31 acknowledges the named packages within its stated handoff scope. The nominated technical reviewer has not returned the applicable requirement-and-evidence decision, TA31. The site arrival does not resolve the missing order line, revise CR31 or fill TA31. The earlier EX-IN-04 example remains the guide to distinguishing package and item populations.

The useful request has two independent parts: obtain the commercial source return that distinguishes P from D, and obtain the material owner's reconciliation of the unresolved order line. Record what each response actually supports. A complete CR31 would not make RR31 a contents inspection; an item reconciliation would not turn CU31 into system acceptance. Keep any technical decision with its nominated reviewer and actual requirements. Do not use this comparison to infer risk passage, ownership, cargo cover, payment, a claim or a remedy; risk-related information also does not decide whether other rights or remedies exist.

Share actual order and shipment details through authorized project channels. Leviathan can discuss the separately agreed receiving and physical documentation scope. This example neither assigns a carrier, warehouse or commercial-advisory role nor supplies a handling, opening, unloading or acceptance procedure.

Incoterms® is ICC's trademark; copyright in the Rules belongs to ICC. This independent article is neither affiliated with nor approved or sponsored by ICC. [ICC-IP]

References: [ICC-I2020][ICC-IP]

Scroll the table horizontally on smaller screens.

RCV-TERM-31: five fictional records answer different delivery and receiving questions
Record returnedWhat the stipulated record supportsWhat remains unresolvedSource
Q31: quotation names Site D and the declared CPT/2020 carriage basis.The destination and commercial basis stated in that invented quotation.The source-bound agreed delivery point; no site receipt, contents check, title or cargo-cover conclusion follows.Planning analysis
CR31: appointed commercial owner separately returns P and its fictional agreement reference.P is stipulated as the agreed delivery point for this example, separately from D.No ruling on an unseen agreement, actual risk passage, payment, liability or remedy.Planning analysis
RR31: two package references recorded at D; one underlying order line unreconciled.Those packages and their external identifiers are recorded as received.The missing line, unobserved contents and any condition or cause question; the carriage term does not reconcile them.Planning analysis
CU31: nominated custodian acknowledges the named package handoff within the agreed scope.That scoped acknowledgement for the identified packages.No amendment of CR31, title-transfer finding, technical approval or permission to start work.Planning analysis
TA31: nominated technical reviewer has not supplied the applicable requirement-and-evidence decision.Technical acceptance remains pending in the fictional record.Carriage payment, arrival, package count and custody acknowledgement cannot substitute for that decision.Planning analysis

Original invented records and relationships only. No actual contract, shipment, inspection, risk/title/insurance finding, claim, payment or remedy, technical acceptance or authority to perform work is established.

Separate the external observation from the internal check

Record shipment identifiers, package count, visible condition and the documents supplied at receipt. State the limits of the observation. A photograph of an intact crate can support an external-condition record; it cannot establish that the enclosed system has the ordered components or no concealed damage.

If a crate is damaged or identifiers disagree, refer the matter to the customer and supplier through the agreed receiving process. Keep the item identifiable while they decide the next action. Do not open, repair, discard packaging or move equipment merely to clear the dock when those actions need authorization. Shipping configuration, packaging removal and handling methods must come from the applicable OEM and site plan.

Read the shipment list at the correct level

A package count, a system component list and a customer purchase list describe different things. The carrier may record a carton without knowing its contents. An OEM hardware table can describe components already inside a server. A customer order may also include accessories or network assemblies supplied under another delivery reference. Matching the numbers without matching those levels can create a false shortage or hide a real one.

NVIDIA’s DGX B200 guide gives a specific example: it describes a supplied set of six locking power cords, but says that network cables and adaptors are not shipped with the system. A missing network cable in that server shipment therefore needs an order check before it is described as missing OEM-supplied content. The customer may have purchased the network materials separately. This named-system description does not establish another OEM’s shipment contents, the particular order’s completeness or permission to connect a cord.

Use the supplier’s order-specific packing record to relate the package to the expected item. Keep a required installation material visible even when it is not an included server accessory: not supplied with the server does not mean not needed for the project. The appointed design and supply owners still determine which actual assemblies are approved and how they reach the site. A receiving record does not select a substitute.

References: [N1]

Scroll the table horizontally on smaller screens.

Published DGX B200 example versus actual receiving evidence
ReferenceWhat it establishesWhat the receiving owner still needsSource
DGX B200 locking-cord descriptionThe guide describes six supplied locking power cords for this system.The actual packing record, applicable system/order and permitted observation of the delivered contents.[N1]
DGX B200 network-cable statementThe guide says network cables and adaptors are not shipped with the system.The customer’s separate supply/order record for the required approved network materials.[N1]
Carrier package entryA logistics record can identify a received package.Its relationship to the expected server, accessory or separate material line; contents and condition are not proved by the entry alone.Planning analysis

Two narrow manufacturer facts with source anchors; the carrier row is original buyer analysis. No actual order, cord compatibility, connection method, equipment count, inspection result or shipment acceptance is verified.

Use a custody record that survives the move

Use one shipment reference from delivery through staging and installation. Record the equipment serial number when it becomes accessible under the authorized process, and distinguish a packaging identifier from an asset identifier. Each handoff should show who released the item, who received it, its location and any unresolved condition.

The worksheet below is an original planning example. Add only fields that the project will actually maintain. Do not include private customer details in public photographs or attach credentials to the receiving record.

Scroll the table horizontally on smaller screens.

Receiving and staging handoff fields
FieldRecordWhy it mattersSource
IdentityShipment reference; package ID; accessible asset serialConnects delivery paperwork to the installed itemPlanning analysis
ConditionObserved condition; observation time; approved photo referenceSeparates evidence from assumptionsPlanning analysis
LocationCurrent approved staging position and intended destinationPrevents an item being lost between teamsPlanning analysis
HoldIssue ID; decision owner; permitted next actionKeeps an unresolved item out of a released workfrontPlanning analysis
CustodyReleasing and receiving roles; time; acknowledgementIdentifies who controls the next movePlanning analysis

Original planning worksheet. Agree the fields and responsibilities for the project; this is not a safety procedure or acceptance standard.

Stage against the installation release, not just the floor plan

Confirm that the proposed staging area is permitted and that the site has approved the movement route, access and handling arrangements for the equipment. Do not infer floor capacity, elevator suitability or a lifting method from a room drawing. Refer those decisions to the authorized facility, OEM and handling specialists.

A rack elevation can show the intended destination while a workfront remains unreleased because its rails, route or access are unresolved. Mark that difference in the logistics record. Sequence customer-furnished equipment and accessories against the released installation tasks; a missing rail kit should appear as a shortage, not an undocumented substitution.

References: [L1]

Worked example: two packages do not close three order lines

Consider fictional purchase EX-IN-04: a server, its accessory kit and a separately ordered network cable bundle. The supplier’s dispatch record associates packages P-A and P-B with the server order. The network supplier has a different shipment reference, N-A. A facility notice reports that two packages have arrived. That notice alone does not establish that every line in the customer’s installation purchase has arrived.

At the permitted external observation, P-A is identifiable and P-B has visible packaging damage. No one has yet been authorized to inspect their contents. The useful status is not all equipment complete or server damaged. It is a record of the two packages, the observed external condition and the unresolved content check. The customer and supplier decide the next permitted action through the agreed process; this example supplies no opening, repair, claim or movement instruction.

If a later authorized check identifies an accessory part different from the packing record, that becomes a specific content discrepancy. Keep the supplier’s expected reference and the observed reference together. If the separate network order N-A has not arrived, record that against its own source rather than invent a shortage inside the server shipment. The two exceptions have different evidence and decision owners, even if both affect the same installation window.

Scroll the table horizontally on smaller screens.

Original EX-IN-04 example: distinguish the unresolved question
Evidence availableConclusion supportedDecision still openSource
Facility notice: P-A and P-B receivedThose two package references are recorded as received.Which expected items the packages contain and whether the contents have been checked.Planning analysis
External observation: damage visible on P-BThe described packaging condition was observed.Internal condition and the supplier/customer’s permitted next action.Planning analysis
Network order: separate shipment N-AThe network materials have their own supply reference.Whether that delivery has arrived and is released for the planned installation.Planning analysis
Later authorized check: observed accessory reference differsA named item differs from its expected packing reference.The supplier/customer disposition; no silent substitution or rewritten original observation.Planning analysis

Original fictional purchasing and custody analysis, not a customer record, OEM packing specification, inspection procedure, claim rule, acceptance criterion or contractual allocation.

Resolve a mismatch without losing traceability

Illustrative example: the manifest lists server A for cabinet C12, but the accessible serial label belongs to the order for C14. Record the observed identifier, the two conflicting references and the customer decision owner. Keep the shipment associated with that issue while the owner checks the order and approved rack plan. A corrected destination should reference the revised instruction, rather than overwriting the original observation.

Before the installation handoff, review open holds, released items and shortages together. Agree who retains the records and who can see photographs. Leviathan can discuss the separately agreed physical installation and documentation package; purchasing materials, warehousing and heavy handling should not be assumed from an installation inquiry.

References: [L1]

Request the document without assuming a contents check

A scanned packing list can help reconcile the expected order with a shipment. It does not show that each listed item was counted, inspected or accepted. Keep the document’s source and the observer’s actual check separate, especially when the list is inside sealed packaging.

Equinix documents an optional scan-and-send manifest/BOM service. Its page says that selecting this option authorizes opening the shipment if the document is not attached outside. This is a narrow, named operator example of why the requested receiving action matters. Confirm the actual facility order and permissions before assuming that someone will obtain an internal document, inspect equipment or preserve packing material. No portal order or customer agreement has been inspected here.

The installation handoff should carry the unresolved content and material issues, not just the transport status. Leviathan can discuss customer-supplied physical installation and the agreed records; receiving, freight, storage and heavy handling are not automatically added to that package. Identify the site and supply owners, describe what has actually been observed, and keep any required authorization or specialist decision open until its owner provides it.

References: [E2][L1][L2]

Common planning questions

Does delivery mean the equipment is accepted for installation?

No. Receipt records delivery; installation release depends on the agreed identity, condition, instructions and site prerequisites.

Should every shipment be opened at the dock?

Use the applicable receiving and OEM instructions, site permission and authorized inspection scope. There is no universal dock-opening rule for all GPU systems.

Does a complete package count prove that all installation materials arrived?

No. Reconcile the package references with the actual server, accessory and separate material orders. A carrier count does not establish item contents, condition or the arrival of a separately supplied cable bundle.

Does a scanned packing list mean the equipment was inspected?

It identifies a document, not necessarily a completed contents or condition check. Confirm which action was requested and authorized, what was actually observed, and which expected-versus-delivered questions remain open.

Primary sources

  1. [E2] Equinix: inbound shipments to an IBXChecked 2026-10-16. Named operator’s receiving model and optional manifest-scan/opening scope only. Actual facility order and permissions control. No deadlines, storage/retention promise, charges, claims/liability or handling method adopted.
  2. [L1] Leviathan rack-and-stack service boundariesChecked 2026-10-16. Current conditional customer-supplied physical scope; no automatic receiving, warehousing, freight, heavy handling or project authority.
  3. [N1] NVIDIA DGX B200: supplied cords and separately supplied network materialsChecked 2026-10-16. Exact named-system shipped-cord and not-shipped network cable/adaptor statements only. No actual order/packing inspection, ratings, methods, compatibility, firmware, startup or transfer to another system.
  4. [L2] Leviathan: Colocation Installation service boundariesChecked 2026-10-16. Receiving, inventory, staging and delivery coordination are project-defined Leviathan services. Specific purchasing, handling and transport arrangements require agreement; no owned warehouse, carrier partnership, facility service, safety or specialist approval is established.
  5. [ICC-I2020] Charles Debattista: personal Introduction to Incoterms® 2020Checked 2026-10-26. 2020-edition explanatory Introduction, especially paragraphs6–15,24–40,78 and author footnote. Personal commentary, not the Rules; destination/delivery distinction only. No actual agreement, applicable-law, risk/title/cover/payment/claims/remedy or rule-selection opinion.
  6. [ICC-IP] ICC: Incoterms® rules trademark and copyright policyChecked 2026-10-26. ICC mark/copyright and non-affiliation acknowledgement only. No Rule text, adapted clause, chart or logo reproduced; public access is not a license or a sponsorship/compliance assurance.

Define the installation handoff

Share the equipment list, delivery arrangements, approved rack plan and open receiving issues so we can discuss the physical scope.

Discuss a ProjectEmail Project Scope