Rackstamp, data center labeling field guide

WORKSHEET 06 / Cables & connectivity

Two-end cable label schedule

Build a paired cable label from two verified termination references and one controlled connection record.

The download includes all 30 worksheets. Open the 06 Cable endpoints tab.

Use it with your own records.

  1. Download the workbook and open 06 Cable endpoints.
  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 06 to complete the checks and record unresolved items.

Before you start

  1. Confirm what the cable ID represents under local policy and whether this batch uses HERE/THERE, fixed A/Z, or an ID-only layout.
  2. Collect the controlled connection row, complete endpoint hierarchy, and permitted evidence for each termination.
  3. Identify the connection owner and separate the authority for identification or installation work from this documentation review.
  4. Preserve any current label text and preliminary candidate destination before preparing a corrected pair.

Complete the register

  1. Enter the exact Cable ID and the connection reference that governs the row, preserving full scope and significant characters.
  2. Enter Local endpoint and Remote endpoint with all required site, hall, rack, equipment, module, and port context.
  3. Link the evidence supporting each endpoint and keep an unverified candidate outside the confirmed endpoint field.
  4. Generate End A text and End B text from the same row. Reverse HERE/THERE descriptions only when that is the selected viewpoint convention.
  5. Record obsolete proofs, reprints, or missing installed reviews in Exception, with an owner and a specific release condition.
  6. Record the independent pair check and actual installed-review outcomes, then enter the verifier, completed review date, and supported status.

Walk through the example

The original fictional connection DEMO-CON-0042 links CAB-0042 from DC01/H1/R014/PP01/07 to DC01/H1/R021/PP02/19. The same cable ID appears on both faces. At end 1, HERE names R014/PP01/07 and THERE names R021/PP02/19; at end 2, those descriptions reverse. Start by validating the complete endpoint references and their supporting evidence, then compare the two proof fields. A repeated final port number elsewhere in the hall does not identify the endpoint without its panel and rack context. DEMO-ENDS-0042 is the fictional evidence reference, not an actual verification. For real work, record the evidence accepted under the site's approved process and keep a remote candidate visibly unresolved until that process establishes it. After authorized application, record the readability and record-closure result for both ends. A matching pair of proofs alone cannot establish the physical relationship or authorize interrupting the connection.

Handle common exceptions

The remote endpoint exists only in a preliminary schedule.

Keep it as an unverified candidate, hold production destination text, and assign the approved identification work.

Both faces show the same HERE endpoint.

Check the generating row and viewpoint mapping, prepare a corrected pair, and account for the superseded proof.

A fixed A/Z label is reported as reversed from the Z end.

Compare the label with the approved fixed-end legend before changing it; clarify the convention if the physical relationship is already correct.

Review and close

  1. Confirm that the cable ID selects the intended record rather than several similar candidates.
  2. Check both complete endpoint references against evidence, not merely against each other.
  3. Read both proofs from their intended viewpoints and verify the chosen convention consistently.
  4. Check visual fit and installed readability using the actual text and approved service view.
  5. Account for stale labels and nearby active references, and keep any unreviewed end pending.

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
Cable IDIdentity shared by the paired labels.CAB-0042
Local endpointFirst complete termination reference.DC01/H1/R014/PP01/07
Remote endpointSecond complete termination reference.DC01/H1/R021/PP02/19
Connection referenceControlled record for this relationship.DEMO-CON-0042
End A textFirst-end label proof.CAB-0042; HERE DC01/H1/R014/PP01/07; THERE DC01/H1/R021/PP02/19
End B textSecond-end label proof.CAB-0042; HERE DC01/H1/R021/PP02/19; THERE DC01/H1/R014/PP01/07
ExceptionUnresolved discrepancy or stated outcome.None in fictional example
OwnerRole responsible for the connection record.Network records lead
EvidenceReferences confirming both terminations.DEMO-ENDS-0042
VerifierPerson comparing both endpoint references.Example reviewer
Verification dateDate the endpoint comparison was made.2026-09-12
StatusIdentification review state.Example only
06 Cable endpoints workbook preview
06 Cable endpoints workbook preview. View full size ↗

Sources and scope