Rackstamp, data center labeling field guide

WORKSHEET 10 / Cables & connectivity

GPU cable staging manifest

Reconcile each cable kit and label pair with a controlled manifest before handing the kit to the deployment team.

The download includes all 30 worksheets. Open the 10 GPU cable staging tab.

Use it with your own records.

  1. Download the workbook and open 10 GPU cable staging.
  2. Enter your site and room scope and the project or policy reference.
  3. Use the blank amber table for actual records. The fictional example below it is a reference.
  4. Insert table rows when needed. Keep identifiers as text, including leading zeros.
  5. Follow guide 10 to complete the checks and record unresolved items.

Before you start

  1. Obtain the released manifest revision and identify its owner, the staging boundary, and the intended receiving owner.
  2. Collect expected cable rows, documented type and length requirements, kit references, and the active label pairs.
  3. Separate staged preparation from installed operational work and preserve any superseded manifest or label discrepancy as evidence.

Complete the register

  1. Enter Manifest revision, Bundle, and Sequence as defined by the released work package, keeping sequence separate from cable identity.
  2. Enter Cable ID and both complete endpoint references from that row.
  3. Compare Type and length with the documented requirement and record proposed substitutions as exceptions awaiting the owner's decision.
  4. Use Kit check to identify the actual kit and the two label faces compared against the row.
  5. Link row-by-row reconciliation, reprint disposition, and any revision-change review in Evidence.
  6. Record the receiving Owner, actual verification date, and a status that distinguishes prepared, held, partial, and reviewed outcomes under the site's process.

Walk through the example

The original fictional bundle B07 contains GPU-0101 in kit K07-01 and GPU-0102 in kit K07-02 under DEMO-GPU revision 4. The first row links DC01/H1/R014/SW1/P01 to DC01/H1/R021/GPU1/NIC1; the second uses its own endpoints and identity. Start by checking the actual governing revision, then compare each kit and both label faces with its row. Expected rows, prepared kits, and label-pair totals all equal two in the example, but those totals are useful only after individual identities agree. DEMO-TYPE-A and 10 m are fictional requirement values, not a GPU-network specification. For real work, retain the released type and length and record substitutions for the deployment owner's decision. Use DEMO-B07-RECON as the illustration of a reconciliation evidence link. The receiving owner and review date must reflect the actual handoff. A completed staging row does not establish installed connectivity or technical readiness.

Handle common exceptions

Counts match but one kit identity appears twice.

Hold the affected group, reconcile individual manifest rows, and resolve the missing and duplicated associations before release.

The kit cover names a superseded manifest revision.

Compare changed fields, recheck affected labels and requirements, and preserve the old review as applying only to its original revision.

A substitute cable is available but not released in the plan.

Record the proposed item separately and obtain the deployment owner's technical and record decision before changing the requirement or releasing the kit.

Review and close

  1. Reconcile expected rows to actual kits and actual kits back to current rows.
  2. Check each shared cable ID and both label faces rather than relying on total label counts.
  3. Confirm that the accepted review applies to the manifest revision named in the handoff.
  4. Account for superseded pairs, missing kits, substitutions, and any installed correction that remains outside staging.
  5. Record the actual handoff contents and receiving owner without implying installation or technical acceptance.

Fields and filled example

Fictional values only. Scope: DC01 / H1 unless another location is shown. The downloadable register is blank for your actual observations.

FieldWhat to recordFictional example
Manifest revisionReleased connection-plan version.DEMO-GPU rev 4
BundleGroup used for staging and handoff.B07
SequenceOrdered position in the local staging plan.01
Cable IDIdentity assigned to this cable.GPU-0101
SourceComplete source equipment and port reference.DC01/H1/R014/SW1/P01
DestinationComplete destination equipment and port reference.DC01/H1/R021/GPU1/NIC1
Type and lengthSpecified cable identity and length.DEMO-TYPE-A / 10 m; fictional
Kit checkKit reference and label-pair comparison.K07-01; pair agrees in example
OwnerRole receiving the reviewed bundle.GPU deployment lead
EvidenceManifest and staging-review references.DEMO-B07-RECON
Verification dateDate the kit reconciliation was completed.2026-09-12
StatusStaging review state.Example only
10 GPU cable staging workbook preview
10 GPU cable staging workbook preview. View full size ↗

Sources and scope

  • NVIDIA: Cable staging ↗

    DGX SuperPOD staging guidance, updated November 19, 2025; this worksheet covers identity reconciliation only. The expanded triage, decision comparisons, scenarios, and closeout procedures are original editorial guidance.

    Read scope and linked guides