{"schemaVersion":1,"version":"0c8fa140edc65330","canonicalBaseUrl":"https://datacenterlabeling.com","siteName":"Rackstamp","language":"en-US","scope":"Rackstamp provides editorial field guidance. IDs, cases, and worksheet entries are fictional examples unless identified otherwise. Distinguish local conventions from adopted standards. Source notes describe the evidence scope; a linked overview is not the full standard or a project approval.","guides":[{"slug":"naming-convention","title":"We do not have a naming convention","dek":"Create a short, usable naming policy that lets another person identify the same object from the same record.","summary":"Start a data center naming convention by defining what each identifier names, where it must be unique, and who can issue it. Record the field meanings, permitted characters, and correction rules, then test examples in the actual labels and records. A standards reference supplies project context; the site's example syntax still needs an explicit local policy and approval.","category":"Naming & location","aliases":[],"canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention","route":"/problems/naming-convention","sourceIds":["S01"],"templateIds":["worksheet-1","site-labeling-standard","multi-site-prefix-register","labeling-handoff-specification","cable-color-legends-planning-template","legacy-room-relabeling-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/duplicate-identifiers","https://datacenterlabeling.com/problems/rack-face-and-u-position","https://datacenterlabeling.com/problems/contractor-labeling-handoff"],"markdownUrl":"https://datacenterlabeling.com/problems/naming-convention.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#quick-answer"},{"id":"which-document-answers-this-labeling-question","title":"Which document answers this labeling question?","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#which-document-answers-this-labeling-question"},{"id":"when-to-use","title":"When to use","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#when-to-use"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#what-to-gather"},{"id":"method","title":"Method","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#method"},{"id":"triage-the-naming-problem-before-choosing-a-format","title":"Triage the naming problem before choosing a format","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#triage-the-naming-problem-before-choosing-a-format"},{"id":"define-the-dictionary-at-the-level-people-actually-use","title":"Define the dictionary at the level people actually use","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#define-the-dictionary-at-the-level-people-actually-use"},{"id":"make-issuance-a-controlled-handoff","title":"Make issuance a controlled handoff","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#make-issuance-a-controlled-handoff"},{"id":"test-the-policy-with-awkward-but-realistic-cases","title":"Test the policy with awkward but realistic cases","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#test-the-policy-with-awkward-but-realistic-cases"},{"id":"introduce-a-convention-into-an-existing-facility","title":"Introduce a convention into an existing facility","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#introduce-a-convention-into-an-existing-facility"},{"id":"scenario-a-service-name-was-mistaken-for-panel-identity","title":"Scenario: a service name was mistaken for panel identity","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#scenario-a-service-name-was-mistaken-for-panel-identity"},{"id":"decide-who-owns-unresolved-naming-questions","title":"Decide who owns unresolved naming questions","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#decide-who-owns-unresolved-naming-questions"},{"id":"turn-a-standards-reference-into-a-reviewable-local-policy","title":"Turn a standards reference into a reviewable local policy","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#turn-a-standards-reference-into-a-reviewable-local-policy"},{"id":"compare-location-rich-and-record-linked-identifiers","title":"Compare location-rich and record-linked identifiers","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#compare-location-rich-and-record-linked-identifiers"},{"id":"work-through-a-naming-change-without-creating-a-second-system","title":"Work through a naming change without creating a second system","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#work-through-a-naming-change-without-creating-a-second-system"},{"id":"define-policy-maintenance-through-concrete-triggers","title":"Define policy maintenance through concrete triggers","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#define-policy-maintenance-through-concrete-triggers"},{"id":"worked-example","title":"Worked example","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#worked-example"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#common-mistakes"},{"id":"verification","title":"Verification","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#verification"},{"id":"worksheet-naming-convention-worksheet","title":"Worksheet: Naming convention worksheet","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#worksheet-naming-convention-worksheet"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/problems/naming-convention#frequently-asked-questions"}]},{"slug":"duplicate-identifiers","title":"Two objects have the same ID","dek":"Separate a duplicate record from a duplicate physical label, then restore one clear identity for each object.","summary":"Resolve a duplicate ID by checking whether it represents two records for one object, two physical objects with one label, or an identifier missing its location scope. Preserve the observed values and evidence before choosing a correction. The accountable owner should approve the retained or replacement identity and close the affected labels, records, and historical crosswalk together.","category":"Naming & location","aliases":[],"canonicalUrl":"https://datacenterlabeling.com/problems/duplicate-identifiers","route":"/problems/duplicate-identifiers","sourceIds":["S02"],"templateIds":["worksheet-2","site-labeling-standard","multi-site-prefix-register","legacy-room-relabeling-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/naming-convention","https://datacenterlabeling.com/problems/bulk-label-import","https://datacenterlabeling.com/problems/label-record-reconciliation"],"markdownUrl":"https://datacenterlabeling.com/problems/duplicate-identifiers.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/duplicate-identifiers#quick-answer"},{"id":"when-to-use","title":"When to use","canonicalUrl":"https://datacenterlabeling.com/problems/duplicate-identifiers#when-to-use"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/duplicate-identifiers#what-to-gather"},{"id":"method","title":"Method","canonicalUrl":"https://datacenterlabeling.com/problems/duplicate-identifiers#method"},{"id":"classify-the-collision-before-deciding-what-to-change","title":"Classify the collision before deciding what to change","canonicalUrl":"https://datacenterlabeling.com/problems/duplicate-identifiers#classify-the-collision-before-deciding-what-to-change"},{"id":"build-an-evidence-set-that-distinguishes-the-objects","title":"Build an evidence set that distinguishes the objects","canonicalUrl":"https://datacenterlabeling.com/problems/duplicate-identifiers#build-an-evidence-set-that-distinguishes-the-objects"},{"id":"choose-the-correction-branch","title":"Choose the correction branch","canonicalUrl":"https://datacenterlabeling.com/problems/duplicate-identifiers#choose-the-correction-branch"},{"id":"trace-the-dependencies-before-making-the-change","title":"Trace the dependencies before making the change","canonicalUrl":"https://datacenterlabeling.com/problems/duplicate-identifiers#trace-the-dependencies-before-making-the-change"},{"id":"scenario-a-duplicate-sticker-on-two-newly-received-assets","title":"Scenario: a duplicate sticker on two newly received assets","canonicalUrl":"https://datacenterlabeling.com/problems/duplicate-identifiers#scenario-a-duplicate-sticker-on-two-newly-received-assets"},{"id":"handle-legacy-inventories-and-new-installations-differently","title":"Handle legacy inventories and new installations differently","canonicalUrl":"https://datacenterlabeling.com/problems/duplicate-identifiers#handle-legacy-inventories-and-new-installations-differently"},{"id":"prove-the-correction-survived-its-normal-inputs","title":"Prove the correction survived its normal inputs","canonicalUrl":"https://datacenterlabeling.com/problems/duplicate-identifiers#prove-the-correction-survived-its-normal-inputs"},{"id":"worked-example","title":"Worked example","canonicalUrl":"https://datacenterlabeling.com/problems/duplicate-identifiers#worked-example"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/duplicate-identifiers#common-mistakes"},{"id":"verification","title":"Verification","canonicalUrl":"https://datacenterlabeling.com/problems/duplicate-identifiers#verification"},{"id":"worksheet-identifier-collision-register","title":"Worksheet: Identifier collision register","canonicalUrl":"https://datacenterlabeling.com/problems/duplicate-identifiers#worksheet-identifier-collision-register"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/problems/duplicate-identifiers#frequently-asked-questions"}]},{"slug":"rack-wayfinding","title":"I cannot find the correct rack","dek":"Make the work-order address, floor map, row signs, and rack labels lead to the same physical destination.","summary":"A usable server-rack label must agree with the work-order address, location map, row signs, and actual approach to the rack. Walk that route from a defined starting point and find the first disagreement. Check front and rear approaches separately, then verify the corrected route with another reader. Keep site and room scope with any shortened rack number.","category":"Naming & location","aliases":[],"canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding","route":"/problems/rack-wayfinding","sourceIds":["S03"],"templateIds":["worksheet-3","multi-site-prefix-register","remote-hands-cabinet-brief","legacy-room-relabeling-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/naming-convention","https://datacenterlabeling.com/problems/rack-face-and-u-position","https://datacenterlabeling.com/problems/colocation-demarcation"],"markdownUrl":"https://datacenterlabeling.com/problems/rack-wayfinding.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding#quick-answer"},{"id":"when-to-use","title":"When to use","canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding#when-to-use"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding#what-to-gather"},{"id":"method","title":"Method","canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding#method"},{"id":"find-the-first-broken-step-in-the-route","title":"Find the first broken step in the route","canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding#find-the-first-broken-step-in-the-route"},{"id":"prepare-a-route-review-that-another-person-can-repeat","title":"Prepare a route review that another person can repeat","canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding#prepare-a-route-review-that-another-person-can-repeat"},{"id":"review-rack-faces-and-viewpoints-explicitly","title":"Review rack faces and viewpoints explicitly","canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding#review-rack-faces-and-viewpoints-explicitly"},{"id":"choose-a-repair-that-addresses-the-cause","title":"Choose a repair that addresses the cause","canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding#choose-a-repair-that-addresses-the-cause"},{"id":"scenario-the-rear-approach-identifies-the-wrong-rack","title":"Scenario: the rear approach identifies the wrong rack","canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding#scenario-the-rear-approach-identifies-the-wrong-rack"},{"id":"work-in-an-established-hall-without-losing-useful-context","title":"Work in an established hall without losing useful context","canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding#work-in-an-established-hall-without-losing-useful-context"},{"id":"capture-evidence-that-supports-an-actual-finding","title":"Capture evidence that supports an actual finding","canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding#capture-evidence-that-supports-an-actual-finding"},{"id":"close-the-route-not-just-the-replacement-sticker","title":"Close the route, not just the replacement sticker","canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding#close-the-route-not-just-the-replacement-sticker"},{"id":"make-server-rack-directions-usable-in-a-changing-data-hall","title":"Make server-rack directions usable in a changing data hall","canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding#make-server-rack-directions-usable-in-a-changing-data-hall"},{"id":"scenario-a-correct-server-name-leads-to-an-obsolete-rack-address","title":"Scenario: a correct server name leads to an obsolete rack address","canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding#scenario-a-correct-server-name-leads-to-an-obsolete-rack-address"},{"id":"connect-containment-doors-rows-and-rack-addresses","title":"Connect containment doors, rows, and rack addresses","canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding#connect-containment-doors-rows-and-rack-addresses"},{"id":"worked-example","title":"Worked example","canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding#worked-example"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding#common-mistakes"},{"id":"verification","title":"Verification","canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding#verification"},{"id":"worksheet-rack-and-row-sign-schedule","title":"Worksheet: Rack and row sign schedule","canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding#worksheet-rack-and-row-sign-schedule"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/problems/rack-wayfinding#frequently-asked-questions"}]},{"slug":"rack-face-and-u-position","title":"Front, rear, and rack units disagree","dek":"Describe the complete equipment footprint so front and rear records point to the same device.","summary":"Record rack position as a complete equipment footprint: rack, mounting face, occupied units, and the rule used for the stored position. Compare both physical faces with the same asset record. A difference between a printed rack number and a database position may reflect different conventions; resolve that translation before moving a label or changing the recorded location.","category":"Naming & location","aliases":["RU rack unit footprint rack elevation"],"canonicalUrl":"https://datacenterlabeling.com/problems/rack-face-and-u-position","route":"/problems/rack-face-and-u-position","sourceIds":["S04"],"templateIds":["worksheet-4","device-label-placement-review","legacy-room-relabeling-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/rack-wayfinding","https://datacenterlabeling.com/problems/asset-versus-location","https://datacenterlabeling.com/problems/patch-panel-port-mapping"],"markdownUrl":"https://datacenterlabeling.com/problems/rack-face-and-u-position.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/rack-face-and-u-position#quick-answer"},{"id":"when-to-use","title":"When to use","canonicalUrl":"https://datacenterlabeling.com/problems/rack-face-and-u-position#when-to-use"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/rack-face-and-u-position#what-to-gather"},{"id":"method","title":"Method","canonicalUrl":"https://datacenterlabeling.com/problems/rack-face-and-u-position#method"},{"id":"separate-a-reference-mismatch-from-an-actual-location-error","title":"Separate a reference mismatch from an actual location error","canonicalUrl":"https://datacenterlabeling.com/problems/rack-face-and-u-position#separate-a-reference-mismatch-from-an-actual-location-error"},{"id":"build-an-observation-that-describes-the-complete-footprint","title":"Build an observation that describes the complete footprint","canonicalUrl":"https://datacenterlabeling.com/problems/rack-face-and-u-position#build-an-observation-that-describes-the-complete-footprint"},{"id":"translate-between-systems-without-rewriting-the-observation","title":"Translate between systems without rewriting the observation","canonicalUrl":"https://datacenterlabeling.com/problems/rack-face-and-u-position#translate-between-systems-without-rewriting-the-observation"},{"id":"treat-mounting-face-and-viewing-face-as-different-facts","title":"Treat mounting face and viewing face as different facts","canonicalUrl":"https://datacenterlabeling.com/problems/rack-face-and-u-position#treat-mounting-face-and-viewing-face-as-different-facts"},{"id":"scenario-a-move-closeout-copied-the-top-visible-unit","title":"Scenario: a move closeout copied the top visible unit","canonicalUrl":"https://datacenterlabeling.com/problems/rack-face-and-u-position#scenario-a-move-closeout-copied-the-top-visible-unit"},{"id":"reconcile-established-racks-and-new-build-elevations","title":"Reconcile established racks and new-build elevations","canonicalUrl":"https://datacenterlabeling.com/problems/rack-face-and-u-position#reconcile-established-racks-and-new-build-elevations"},{"id":"resolve-recurring-failures-at-their-source","title":"Resolve recurring failures at their source","canonicalUrl":"https://datacenterlabeling.com/problems/rack-face-and-u-position#resolve-recurring-failures-at-their-source"},{"id":"record-a-closeout-another-shift-can-follow","title":"Record a closeout another shift can follow","canonicalUrl":"https://datacenterlabeling.com/problems/rack-face-and-u-position#record-a-closeout-another-shift-can-follow"},{"id":"worked-example","title":"Worked example","canonicalUrl":"https://datacenterlabeling.com/problems/rack-face-and-u-position#worked-example"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/rack-face-and-u-position#common-mistakes"},{"id":"verification","title":"Verification","canonicalUrl":"https://datacenterlabeling.com/problems/rack-face-and-u-position#verification"},{"id":"worksheet-rack-elevation-and-label-placement-worksheet","title":"Worksheet: Rack elevation and label-placement worksheet","canonicalUrl":"https://datacenterlabeling.com/problems/rack-face-and-u-position#worksheet-rack-elevation-and-label-placement-worksheet"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/problems/rack-face-and-u-position#frequently-asked-questions"}]},{"slug":"asset-versus-location","title":"Moving a device makes its identity confusing","dek":"Keep the asset's identity traceable while its rack position, hostname, or service assignment changes.","summary":"Keep an asset's identity distinct from its current location and service name. During a move, retain the asset ID unless the governing policy requires otherwise, update the location relationship, and preserve aliases needed to interpret older records. A replaced physical device and a relocated device are different events and need different identity decisions.","category":"Naming & location","aliases":[],"canonicalUrl":"https://datacenterlabeling.com/problems/asset-versus-location","route":"/problems/asset-versus-location","sourceIds":["S04"],"templateIds":["worksheet-5","multi-site-prefix-register","change-ticket-labeling-closeout","remote-hands-cabinet-brief","device-label-placement-review","identification-technology-pilot-plan"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/naming-convention","https://datacenterlabeling.com/problems/label-record-reconciliation","https://datacenterlabeling.com/problems/moves-and-retirement-closeout"],"markdownUrl":"https://datacenterlabeling.com/problems/asset-versus-location.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/asset-versus-location#quick-answer"},{"id":"when-to-use","title":"When to use","canonicalUrl":"https://datacenterlabeling.com/problems/asset-versus-location#when-to-use"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/asset-versus-location#what-to-gather"},{"id":"method","title":"Method","canonicalUrl":"https://datacenterlabeling.com/problems/asset-versus-location#method"},{"id":"decide-whether-the-object-moved-changed-or-was-replaced","title":"Decide whether the object moved, changed, or was replaced","canonicalUrl":"https://datacenterlabeling.com/problems/asset-versus-location#decide-whether-the-object-moved-changed-or-was-replaced"},{"id":"build-a-before-planned-and-observed-record","title":"Build a before, planned, and observed record","canonicalUrl":"https://datacenterlabeling.com/problems/asset-versus-location#build-a-before-planned-and-observed-record"},{"id":"keep-identity-fields-and-aliases-in-a-usable-crosswalk","title":"Keep identity fields and aliases in a usable crosswalk","canonicalUrl":"https://datacenterlabeling.com/problems/asset-versus-location#keep-identity-fields-and-aliases-in-a-usable-crosswalk"},{"id":"follow-the-move-through-dependent-records","title":"Follow the move through dependent records","canonicalUrl":"https://datacenterlabeling.com/problems/asset-versus-location#follow-the-move-through-dependent-records"},{"id":"scenario-a-moved-device-also-receives-a-new-hostname","title":"Scenario: a moved device also receives a new hostname","canonicalUrl":"https://datacenterlabeling.com/problems/asset-versus-location#scenario-a-moved-device-also-receives-a-new-hostname"},{"id":"handle-replacement-and-partial-moves-without-losing-history","title":"Handle replacement and partial moves without losing history","canonicalUrl":"https://datacenterlabeling.com/problems/asset-versus-location#handle-replacement-and-partial-moves-without-losing-history"},{"id":"work-with-incomplete-legacy-evidence","title":"Work with incomplete legacy evidence","canonicalUrl":"https://datacenterlabeling.com/problems/asset-versus-location#work-with-incomplete-legacy-evidence"},{"id":"review-the-completed-history-from-both-directions","title":"Review the completed history from both directions","canonicalUrl":"https://datacenterlabeling.com/problems/asset-versus-location#review-the-completed-history-from-both-directions"},{"id":"worked-example","title":"Worked example","canonicalUrl":"https://datacenterlabeling.com/problems/asset-versus-location#worked-example"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/asset-versus-location#common-mistakes"},{"id":"verification","title":"Verification","canonicalUrl":"https://datacenterlabeling.com/problems/asset-versus-location#verification"},{"id":"worksheet-asset-to-location-crosswalk","title":"Worksheet: Asset-to-location crosswalk","canonicalUrl":"https://datacenterlabeling.com/problems/asset-versus-location#worksheet-asset-to-location-crosswalk"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/problems/asset-versus-location#frequently-asked-questions"}]},{"slug":"cable-endpoint-identification","title":"I cannot identify the other cable end","dek":"Build a paired cable label from two verified termination references and one controlled connection record.","summary":"Identify a cable through one controlled connection record with two verified endpoint references. Each endpoint needs enough site, rack, device or panel, and port context to select the intended termination. Produce both labels from that record using one declared local/remote or fixed-end convention. If the far end is unverified, record the uncertainty instead of printing a plausible destination as fact.","category":"Cables & connectivity","aliases":["far end other end remote end trace termination"],"canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification","route":"/problems/cable-endpoint-identification","sourceIds":["S05"],"templateIds":["worksheet-6","change-ticket-labeling-closeout","remote-hands-cabinet-brief","panel-port-relationship-schedule","label-printer-selection-plan","identification-technology-pilot-plan","cable-color-legends-planning-template","legacy-room-relabeling-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/patch-panel-port-mapping","https://datacenterlabeling.com/problems/dense-rack-label-visibility","https://datacenterlabeling.com/problems/label-record-reconciliation"],"markdownUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#quick-answer"},{"id":"what-must-agree-on-the-two-cable-labels","title":"What must agree on the two cable labels?","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#what-must-agree-on-the-two-cable-labels"},{"id":"when-to-use","title":"When to use","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#when-to-use"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#what-to-gather"},{"id":"method","title":"Method","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#method"},{"id":"identify-which-part-of-the-endpoint-relationship-is-missing","title":"Identify which part of the endpoint relationship is missing","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#identify-which-part-of-the-endpoint-relationship-is-missing"},{"id":"decide-what-the-cable-identity-means","title":"Decide what the cable identity means","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#decide-what-the-cable-identity-means"},{"id":"build-a-complete-endpoint-reference","title":"Build a complete endpoint reference","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#build-a-complete-endpoint-reference"},{"id":"choose-one-label-reading-convention","title":"Choose one label-reading convention","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#choose-one-label-reading-convention"},{"id":"establish-evidence-for-both-ends","title":"Establish evidence for both ends","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#establish-evidence-for-both-ends"},{"id":"produce-the-pair-from-one-controlled-row","title":"Produce the pair from one controlled row","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#produce-the-pair-from-one-controlled-row"},{"id":"review-reciprocal-labels-without-relying-on-familiarity","title":"Review reciprocal labels without relying on familiarity","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#review-reciprocal-labels-without-relying-on-familiarity"},{"id":"scenario-a-plausible-remote-switch-name-was-wrong","title":"Scenario: a plausible remote switch name was wrong","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#scenario-a-plausible-remote-switch-name-was-wrong"},{"id":"scenario-fixed-endpoints-were-mistaken-for-local-endpoints","title":"Scenario: fixed endpoints were mistaken for local endpoints","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#scenario-fixed-endpoints-were-mistaken-for-local-endpoints"},{"id":"handle-patch-cords-permanent-runs-and-intermediate-connections-explicitly","title":"Handle patch cords, permanent runs, and intermediate connections explicitly","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#handle-patch-cords-permanent-runs-and-intermediate-connections-explicitly"},{"id":"repair-brownfield-records-and-prepare-new-build-handoffs","title":"Repair brownfield records and prepare new-build handoffs","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#repair-brownfield-records-and-prepare-new-build-handoffs"},{"id":"troubleshoot-recurring-text-and-layout-failures","title":"Troubleshoot recurring text and layout failures","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#troubleshoot-recurring-text-and-layout-failures"},{"id":"worked-example","title":"Worked example","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#worked-example"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#common-mistakes"},{"id":"verification","title":"Verification","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#verification"},{"id":"worksheet-two-end-cable-label-schedule","title":"Worksheet: Two-end cable label schedule","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#worksheet-two-end-cable-label-schedule"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/problems/cable-endpoint-identification#frequently-asked-questions"}]},{"slug":"patch-panel-port-mapping","title":"Patch-panel and port labels do not match","dek":"Reconcile the manufacturer's port references with the panel record and a full-size printed proof.","summary":"Start a patch-panel label with the panel's identity and the manufacturer's port references. Reconcile those references with the port map, then measure the actual layout and inspect a full-size printed proof. Treat a wrong port relationship and a drifting strip as separate defects. There is no single label size or numbering template that fits every panel.","category":"Cables & connectivity","aliases":[],"canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping","route":"/problems/patch-panel-port-mapping","sourceIds":["S06"],"templateIds":["worksheet-7","patch-panel-print-proof","panel-port-relationship-schedule","label-printer-selection-plan","identification-technology-pilot-plan","legacy-room-relabeling-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/rack-face-and-u-position","https://datacenterlabeling.com/problems/cable-endpoint-identification","https://datacenterlabeling.com/problems/label-print-quality"],"markdownUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#quick-answer"},{"id":"what-does-the-strip-s-error-pattern-tell-you","title":"What does the strip's error pattern tell you?","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#what-does-the-strip-s-error-pattern-tell-you"},{"id":"when-to-use","title":"When to use","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#when-to-use"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#what-to-gather"},{"id":"method","title":"Method","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#method"},{"id":"separate-mapping-errors-from-printing-errors","title":"Separate mapping errors from printing errors","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#separate-mapping-errors-from-printing-errors"},{"id":"define-the-full-record-key-for-a-port","title":"Define the full record key for a port","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#define-the-full-record-key-for-a-port"},{"id":"choose-the-information-the-physical-strip-needs-to-carry","title":"Choose the information the physical strip needs to carry","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#choose-the-information-the-physical-strip-needs-to-carry"},{"id":"capture-geometry-with-defined-terms-and-units","title":"Capture geometry with defined terms and units","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#capture-geometry-with-defined-terms-and-units"},{"id":"prepare-an-editable-source-without-losing-the-port-references","title":"Prepare an editable source without losing the port references","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#prepare-an-editable-source-without-losing-the-port-references"},{"id":"select-a-template-or-software-by-the-mapping-it-can-preserve","title":"Select a template or software by the mapping it can preserve","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#select-a-template-or-software-by-the-mapping-it-can-preserve"},{"id":"inspect-an-actual-size-proof-in-the-panel-context","title":"Inspect an actual-size proof in the panel context","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#inspect-an-actual-size-proof-in-the-panel-context"},{"id":"use-the-error-pattern-to-choose-the-next-correction","title":"Use the error pattern to choose the next correction","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#use-the-error-pattern-to-choose-the-next-correction"},{"id":"scenario-the-second-group-drifts-while-the-first-group-aligns","title":"Scenario: the second group drifts while the first group aligns","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#scenario-the-second-group-drifts-while-the-first-group-aligns"},{"id":"scenario-repeated-port-01-values-lost-their-module-context","title":"Scenario: repeated port 01 values lost their module context","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#scenario-repeated-port-01-values-lost-their-module-context"},{"id":"adapt-the-process-to-brownfield-repairs-and-new-builds","title":"Adapt the process to brownfield repairs and new builds","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#adapt-the-process-to-brownfield-repairs-and-new-builds"},{"id":"close-the-map-and-preserve-reproducibility","title":"Close the map and preserve reproducibility","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#close-the-map-and-preserve-reproducibility"},{"id":"build-a-port-strip-from-measured-geometry","title":"Build a port strip from measured geometry","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#build-a-port-strip-from-measured-geometry"},{"id":"worked-example","title":"Worked example","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#worked-example"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#common-mistakes"},{"id":"verification","title":"Verification","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#verification"},{"id":"worksheet-patch-panel-map-and-strip-proof-sheet","title":"Worksheet: Patch-panel map and strip proof sheet","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#worksheet-patch-panel-map-and-strip-proof-sheet"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/problems/patch-panel-port-mapping#frequently-asked-questions"}]},{"slug":"fiber-trunk-breakout-map","title":"Fiber trunks and breakout legs are ambiguous","dek":"Give every leg or fiber a traceable relationship to its assembly, local hierarchy, and remote termination.","summary":"Map a fiber breakout from its parent assembly and controlling revision through each required leg or fiber to the exact remote endpoint. Preserve module and cassette context where short references repeat. Keep unused positions visible with a defined status. Identity mapping and polarity evidence answer different questions; a complete label register does not by itself establish the assembly's technical performance.","category":"Cables & connectivity","aliases":["MTP MPO cassette fanout polarity"],"canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map","route":"/problems/fiber-trunk-breakout-map","sourceIds":["S07"],"templateIds":["worksheet-8","fiber-assembly-reference-record","panel-port-relationship-schedule","cable-color-legends-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/cable-endpoint-identification","https://datacenterlabeling.com/problems/patch-panel-port-mapping","https://datacenterlabeling.com/problems/gpu-cable-staging"],"markdownUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#quick-answer"},{"id":"how-should-a-missing-or-unused-fiber-reference-be-recorded","title":"How should a missing or unused fiber reference be recorded?","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#how-should-a-missing-or-unused-fiber-reference-be-recorded"},{"id":"when-to-use","title":"When to use","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#when-to-use"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#what-to-gather"},{"id":"method","title":"Method","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#method"},{"id":"determine-what-is-actually-ambiguous","title":"Determine what is actually ambiguous","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#determine-what-is-actually-ambiguous"},{"id":"establish-the-parent-assembly-and-controlling-revision","title":"Establish the parent assembly and controlling revision","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#establish-the-parent-assembly-and-controlling-revision"},{"id":"keep-trunk-leg-fiber-and-port-terms-distinct","title":"Keep trunk, leg, fiber, and port terms distinct","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#keep-trunk-leg-fiber-and-port-terms-distinct"},{"id":"capture-the-hierarchy-on-both-sides","title":"Capture the hierarchy on both sides","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#capture-the-hierarchy-on-both-sides"},{"id":"account-for-every-required-reference","title":"Account for every required reference","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#account-for-every-required-reference"},{"id":"build-a-readable-diagram-from-the-verified-register","title":"Build a readable diagram from the verified register","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#build-a-readable-diagram-from-the-verified-register"},{"id":"compare-identity-mapping-with-separate-technical-evidence","title":"Compare identity mapping with separate technical evidence","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#compare-identity-mapping-with-separate-technical-evidence"},{"id":"scenario-a-reused-diagram-points-a-leg-to-the-wrong-switch","title":"Scenario: a reused diagram points a leg to the wrong switch","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#scenario-a-reused-diagram-points-a-leg-to-the-wrong-switch"},{"id":"scenario-two-cassette-references-look-identical-in-an-export","title":"Scenario: two cassette references look identical in an export","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#scenario-two-cassette-references-look-identical-in-an-export"},{"id":"handle-brownfield-uncertainty-and-new-build-preparation","title":"Handle brownfield uncertainty and new-build preparation","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#handle-brownfield-uncertainty-and-new-build-preparation"},{"id":"close-a-complete-and-interpretable-mapping-record","title":"Close a complete and interpretable mapping record","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#close-a-complete-and-interpretable-mapping-record"},{"id":"worked-example","title":"Worked example","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#worked-example"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#common-mistakes"},{"id":"verification","title":"Verification","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#verification"},{"id":"worksheet-fiber-trunk-and-breakout-mapping-sheet","title":"Worksheet: Fiber trunk and breakout mapping sheet","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#worksheet-fiber-trunk-and-breakout-mapping-sheet"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/problems/fiber-trunk-breakout-map#frequently-asked-questions"}]},{"slug":"dense-rack-label-visibility","title":"Labels disappear inside dense bundles","dek":"Evaluate label format and placement from the position where the identifier must actually be read.","summary":"Judge a cable label from the position where someone must read it during permitted work. Record the cable geometry, marker, viewing direction, and nearby obstructions before choosing a wrap, flag, or placement change. Check the installed sample in the intended service view. A label that is readable before bundling may still be inaccessible after installation.","category":"Cables & connectivity","aliases":["flag wrap hidden unreadable"],"canonicalUrl":"https://datacenterlabeling.com/problems/dense-rack-label-visibility","route":"/problems/dense-rack-label-visibility","sourceIds":["S08"],"templateIds":["worksheet-9","fiber-assembly-reference-record","device-label-placement-review"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/cable-endpoint-identification","https://datacenterlabeling.com/problems/label-material-failure","https://datacenterlabeling.com/problems/label-fit-and-readability"],"markdownUrl":"https://datacenterlabeling.com/problems/dense-rack-label-visibility.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/dense-rack-label-visibility#quick-answer"},{"id":"when-to-use","title":"When to use","canonicalUrl":"https://datacenterlabeling.com/problems/dense-rack-label-visibility#when-to-use"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/dense-rack-label-visibility#what-to-gather"},{"id":"method","title":"Method","canonicalUrl":"https://datacenterlabeling.com/problems/dense-rack-label-visibility#method"},{"id":"define-the-reading-task-before-choosing-another-marker","title":"Define the reading task before choosing another marker","canonicalUrl":"https://datacenterlabeling.com/problems/dense-rack-label-visibility#define-the-reading-task-before-choosing-another-marker"},{"id":"gather-the-conditions-that-make-this-location-difficult","title":"Gather the conditions that make this location difficult","canonicalUrl":"https://datacenterlabeling.com/problems/dense-rack-label-visibility#gather-the-conditions-that-make-this-location-difficult"},{"id":"compare-formats-by-the-complete-service-task","title":"Compare formats by the complete service task","canonicalUrl":"https://datacenterlabeling.com/problems/dense-rack-label-visibility#compare-formats-by-the-complete-service-task"},{"id":"review-the-dressed-sample-without-creating-a-misleading-view","title":"Review the dressed sample without creating a misleading view","canonicalUrl":"https://datacenterlabeling.com/problems/dense-rack-label-visibility#review-the-dressed-sample-without-creating-a-misleading-view"},{"id":"decide-when-a-supplemental-reference-is-useful","title":"Decide when a supplemental reference is useful","canonicalUrl":"https://datacenterlabeling.com/problems/dense-rack-label-visibility#decide-when-a-supplemental-reference-is-useful"},{"id":"scenario-a-readable-loose-label-disappears-after-dressing","title":"Scenario: a readable loose label disappears after dressing","canonicalUrl":"https://datacenterlabeling.com/problems/dense-rack-label-visibility#scenario-a-readable-loose-label-disappears-after-dressing"},{"id":"scenario-endpoint-detail-moves-to-a-controlled-rack-reference","title":"Scenario: endpoint detail moves to a controlled rack reference","canonicalUrl":"https://datacenterlabeling.com/problems/dense-rack-label-visibility#scenario-endpoint-detail-moves-to-a-controlled-rack-reference"},{"id":"apply-the-review-across-existing-and-new-installations","title":"Apply the review across existing and new installations","canonicalUrl":"https://datacenterlabeling.com/problems/dense-rack-label-visibility#apply-the-review-across-existing-and-new-installations"},{"id":"close-with-a-reproducible-placement-record","title":"Close with a reproducible placement record","canonicalUrl":"https://datacenterlabeling.com/problems/dense-rack-label-visibility#close-with-a-reproducible-placement-record"},{"id":"worked-example","title":"Worked example","canonicalUrl":"https://datacenterlabeling.com/problems/dense-rack-label-visibility#worked-example"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/dense-rack-label-visibility#common-mistakes"},{"id":"verification","title":"Verification","canonicalUrl":"https://datacenterlabeling.com/problems/dense-rack-label-visibility#verification"},{"id":"worksheet-dense-rack-placement-checklist","title":"Worksheet: Dense-rack placement checklist","canonicalUrl":"https://datacenterlabeling.com/problems/dense-rack-label-visibility#worksheet-dense-rack-placement-checklist"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/problems/dense-rack-label-visibility#frequently-asked-questions"}]},{"slug":"gpu-cable-staging","title":"GPU cable bundles lose their installation sequence","dek":"Reconcile each cable kit and label pair with a controlled manifest before handing the kit to the deployment team.","summary":"Build GPU cable kits from a released manifest that keeps cable identity, source, destination, assembly type, and installation sequence together. Check the kit and both label ends against that revision before handoff. Record substitutions and incomplete kits as exceptions; a staging sequence helps installation but should not become an undocumented replacement for the cable's identity.","category":"Cables & connectivity","aliases":[],"canonicalUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging","route":"/problems/gpu-cable-staging","sourceIds":["S09"],"templateIds":["worksheet-10"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/fiber-trunk-breakout-map","https://datacenterlabeling.com/problems/bulk-label-import","https://datacenterlabeling.com/problems/contractor-labeling-handoff"],"markdownUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging#quick-answer"},{"id":"when-to-use","title":"When to use","canonicalUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging#when-to-use"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging#what-to-gather"},{"id":"method","title":"Method","canonicalUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging#method"},{"id":"identify-whether-the-problem-is-revision-identity-or-sequence","title":"Identify whether the problem is revision, identity, or sequence","canonicalUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging#identify-whether-the-problem-is-revision-identity-or-sequence"},{"id":"establish-one-reviewable-source-of-preparation-data","title":"Establish one reviewable source of preparation data","canonicalUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging#establish-one-reviewable-source-of-preparation-data"},{"id":"keep-the-cable-its-two-labels-and-its-kit-reference-together","title":"Keep the cable, its two labels, and its kit reference together","canonicalUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging#keep-the-cable-its-two-labels-and-its-kit-reference-together"},{"id":"reconcile-identities-before-relying-on-totals","title":"Reconcile identities before relying on totals","canonicalUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging#reconcile-identities-before-relying-on-totals"},{"id":"manage-manifest-changes-as-a-scoped-recheck","title":"Manage manifest changes as a scoped recheck","canonicalUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging#manage-manifest-changes-as-a-scoped-recheck"},{"id":"scenario-counts-agree-but-one-cable-kit-is-duplicated","title":"Scenario: counts agree but one cable kit is duplicated","canonicalUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging#scenario-counts-agree-but-one-cable-kit-is-duplicated"},{"id":"scenario-a-destination-changed-after-the-labels-were-printed","title":"Scenario: a destination changed after the labels were printed","canonicalUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging#scenario-a-destination-changed-after-the-labels-were-printed"},{"id":"handoff-a-partial-bundle-honestly","title":"Handoff a partial bundle honestly","canonicalUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging#handoff-a-partial-bundle-honestly"},{"id":"adapt-preparation-to-existing-halls-and-new-deployments","title":"Adapt preparation to existing halls and new deployments","canonicalUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging#adapt-preparation-to-existing-halls-and-new-deployments"},{"id":"close-with-evidence-that-can-be-checked-after-handoff","title":"Close with evidence that can be checked after handoff","canonicalUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging#close-with-evidence-that-can-be-checked-after-handoff"},{"id":"worked-example","title":"Worked example","canonicalUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging#worked-example"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging#common-mistakes"},{"id":"verification","title":"Verification","canonicalUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging#verification"},{"id":"worksheet-gpu-cable-staging-manifest","title":"Worksheet: GPU cable staging manifest","canonicalUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging#worksheet-gpu-cable-staging-manifest"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/problems/gpu-cable-staging#frequently-asked-questions"}]},{"slug":"a-b-power-feed-identification","title":"A and B feeds are easy to confuse","dek":"Give each feed a clear textual identity and reconcile it with the approved power-path record.","summary":"Give each power path an explicit textual designation and reconcile it with the approved power-path record. Keep PDU identity, upstream source, and any local color legend connected. An A/B label or two different colors does not prove that supplies are independent. Route uncertain power-path relationships to the responsible electrical owner and record the unresolved evidence.","category":"Power & safety","aliases":["A/B dual power feed redundancy"],"canonicalUrl":"https://datacenterlabeling.com/problems/a-b-power-feed-identification","route":"/problems/a-b-power-feed-identification","sourceIds":["S10","S14"],"templateIds":["worksheet-11","remote-hands-cabinet-brief","cable-color-legends-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking","https://datacenterlabeling.com/problems/pdu-outlet-psu-map","https://datacenterlabeling.com/problems/operational-versus-safety-labels"],"markdownUrl":"https://datacenterlabeling.com/problems/a-b-power-feed-identification.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/a-b-power-feed-identification#quick-answer"},{"id":"when-to-use","title":"When to use","canonicalUrl":"https://datacenterlabeling.com/problems/a-b-power-feed-identification#when-to-use"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/a-b-power-feed-identification#what-to-gather"},{"id":"identification-workflow","title":"Identification workflow","canonicalUrl":"https://datacenterlabeling.com/problems/a-b-power-feed-identification#identification-workflow"},{"id":"choose-the-starting-branch","title":"Choose the starting branch","canonicalUrl":"https://datacenterlabeling.com/problems/a-b-power-feed-identification#choose-the-starting-branch"},{"id":"build-the-evidence-packet-before-drafting-text","title":"Build the evidence packet before drafting text","canonicalUrl":"https://datacenterlabeling.com/problems/a-b-power-feed-identification#build-the-evidence-packet-before-drafting-text"},{"id":"turn-the-comparison-into-specific-decisions","title":"Turn the comparison into specific decisions","canonicalUrl":"https://datacenterlabeling.com/problems/a-b-power-feed-identification#turn-the-comparison-into-specific-decisions"},{"id":"worked-case-a-copied-template-repeats-the-wrong-feed","title":"Worked case: a copied template repeats the wrong feed","canonicalUrl":"https://datacenterlabeling.com/problems/a-b-power-feed-identification#worked-case-a-copied-template-repeats-the-wrong-feed"},{"id":"variations-that-need-an-explicit-record-choice","title":"Variations that need an explicit record choice","canonicalUrl":"https://datacenterlabeling.com/problems/a-b-power-feed-identification#variations-that-need-an-explicit-record-choice"},{"id":"evidence-needed-to-close-the-discrepancy","title":"Evidence needed to close the discrepancy","canonicalUrl":"https://datacenterlabeling.com/problems/a-b-power-feed-identification#evidence-needed-to-close-the-discrepancy"},{"id":"join-the-documented-power-chain-through-the-whip","title":"Join the documented power chain through the whip","canonicalUrl":"https://datacenterlabeling.com/problems/a-b-power-feed-identification#join-the-documented-power-chain-through-the-whip"},{"id":"worked-example","title":"Worked example","canonicalUrl":"https://datacenterlabeling.com/problems/a-b-power-feed-identification#worked-example"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/a-b-power-feed-identification#common-mistakes"},{"id":"verification","title":"Verification","canonicalUrl":"https://datacenterlabeling.com/problems/a-b-power-feed-identification#verification"},{"id":"worksheet-a-b-feed-identification-worksheet","title":"Worksheet: A/B feed identification worksheet","canonicalUrl":"https://datacenterlabeling.com/problems/a-b-power-feed-identification#worksheet-a-b-feed-identification-worksheet"},{"id":"faqs","title":"FAQs","canonicalUrl":"https://datacenterlabeling.com/problems/a-b-power-feed-identification#faqs"}]},{"slug":"panel-circuit-disconnect-marking","title":"The supplying circuit or disconnect is unclear","dek":"Document the marking discrepancy precisely and give the electrical owner the evidence needed to resolve it.","summary":"Survey an unclear circuit or disconnect marking by recording the exact equipment, location, observed text, and conflicting document reference. Preserve the discrepancy for the responsible electrical owner to resolve. An identification survey does not authorize operation of a disconnect or establish an electrically safe work condition; close the record against the approved marking decision and its evidence.","category":"Power & safety","aliases":[],"canonicalUrl":"https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking","route":"/problems/panel-circuit-disconnect-marking","sourceIds":["S11","S32"],"templateIds":["worksheet-12","legacy-room-relabeling-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/a-b-power-feed-identification","https://datacenterlabeling.com/problems/pdu-outlet-psu-map","https://datacenterlabeling.com/problems/operational-versus-safety-labels"],"markdownUrl":"https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking#quick-answer"},{"id":"when-to-use","title":"When to use","canonicalUrl":"https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking#when-to-use"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking#what-to-gather"},{"id":"identification-workflow","title":"Identification workflow","canonicalUrl":"https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking#identification-workflow"},{"id":"decide-what-the-survey-has-actually-found","title":"Decide what the survey has actually found","canonicalUrl":"https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking#decide-what-the-survey-has-actually-found"},{"id":"gather-evidence-that-distinguishes-similar-references","title":"Gather evidence that distinguishes similar references","canonicalUrl":"https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking#gather-evidence-that-distinguishes-similar-references"},{"id":"prepare-a-correction-that-the-reviewer-can-assess","title":"Prepare a correction that the reviewer can assess","canonicalUrl":"https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking#prepare-a-correction-that-the-reviewer-can-assess"},{"id":"worked-case-a-disconnect-id-is-present-but-purpose-is-missing","title":"Worked case: a disconnect ID is present but purpose is missing","canonicalUrl":"https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking#worked-case-a-disconnect-id-is-present-but-purpose-is-missing"},{"id":"variations-that-change-the-record-not-the-survey-s-authority","title":"Variations that change the record, not the survey's authority","canonicalUrl":"https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking#variations-that-change-the-record-not-the-survey-s-authority"},{"id":"failure-patterns-and-the-evidence-needed-for-closure","title":"Failure patterns and the evidence needed for closure","canonicalUrl":"https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking#failure-patterns-and-the-evidence-needed-for-closure"},{"id":"keep-emergency-shutoff-scope-and-directory-changes-under-named-owners","title":"Keep emergency shutoff scope and directory changes under named owners","canonicalUrl":"https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking#keep-emergency-shutoff-scope-and-directory-changes-under-named-owners"},{"id":"reconcile-several-panel-directory-entries-without-hiding-exceptions","title":"Reconcile several panel-directory entries without hiding exceptions","canonicalUrl":"https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking#reconcile-several-panel-directory-entries-without-hiding-exceptions"},{"id":"worked-example","title":"Worked example","canonicalUrl":"https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking#worked-example"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking#common-mistakes"},{"id":"verification","title":"Verification","canonicalUrl":"https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking#verification"},{"id":"worksheet-circuit-and-disconnect-marking-survey","title":"Worksheet: Circuit and disconnect marking survey","canonicalUrl":"https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking#worksheet-circuit-and-disconnect-marking-survey"},{"id":"faqs","title":"FAQs","canonicalUrl":"https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking#faqs"}]},{"slug":"pdu-outlet-psu-map","title":"PDU outlets cannot be matched to device power supplies","dek":"Record the exact cord, outlet, and device inlet as one connection relationship.","summary":"Map a device power connection as one relationship between a particular cord, PDU outlet, and marked device PSU or inlet. Use the actual outlet and inlet identifiers rather than assuming order from their physical positions. Reconcile both ends with the approved record, and keep outlet identity separate from the PDU's overall A/B feed designation.","category":"Power & safety","aliases":[],"canonicalUrl":"https://datacenterlabeling.com/problems/pdu-outlet-psu-map","route":"/problems/pdu-outlet-psu-map","sourceIds":["S12"],"templateIds":["worksheet-13","remote-hands-cabinet-brief"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/a-b-power-feed-identification","https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking","https://datacenterlabeling.com/problems/label-record-reconciliation"],"markdownUrl":"https://datacenterlabeling.com/problems/pdu-outlet-psu-map.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/pdu-outlet-psu-map#quick-answer"},{"id":"when-to-use","title":"When to use","canonicalUrl":"https://datacenterlabeling.com/problems/pdu-outlet-psu-map#when-to-use"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/pdu-outlet-psu-map#what-to-gather"},{"id":"identification-workflow","title":"Identification workflow","canonicalUrl":"https://datacenterlabeling.com/problems/pdu-outlet-psu-map#identification-workflow"},{"id":"choose-the-relationship-that-needs-review","title":"Choose the relationship that needs review","canonicalUrl":"https://datacenterlabeling.com/problems/pdu-outlet-psu-map#choose-the-relationship-that-needs-review"},{"id":"establish-the-endpoint-vocabulary-before-following-the-record","title":"Establish the endpoint vocabulary before following the record","canonicalUrl":"https://datacenterlabeling.com/problems/pdu-outlet-psu-map#establish-the-endpoint-vocabulary-before-following-the-record"},{"id":"reconcile-one-cord-without-losing-competing-information","title":"Reconcile one cord without losing competing information","canonicalUrl":"https://datacenterlabeling.com/problems/pdu-outlet-psu-map#reconcile-one-cord-without-losing-competing-information"},{"id":"worked-case-an-old-hostname-hides-the-correct-inlet","title":"Worked case: an old hostname hides the correct inlet","canonicalUrl":"https://datacenterlabeling.com/problems/pdu-outlet-psu-map#worked-case-an-old-hostname-hides-the-correct-inlet"},{"id":"adapt-the-record-when-the-installation-changes","title":"Adapt the record when the installation changes","canonicalUrl":"https://datacenterlabeling.com/problems/pdu-outlet-psu-map#adapt-the-record-when-the-installation-changes"},{"id":"close-with-endpoint-evidence-not-just-label-quantities","title":"Close with endpoint evidence, not just label quantities","canonicalUrl":"https://datacenterlabeling.com/problems/pdu-outlet-psu-map#close-with-endpoint-evidence-not-just-label-quantities"},{"id":"worked-example","title":"Worked example","canonicalUrl":"https://datacenterlabeling.com/problems/pdu-outlet-psu-map#worked-example"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/pdu-outlet-psu-map#common-mistakes"},{"id":"verification","title":"Verification","canonicalUrl":"https://datacenterlabeling.com/problems/pdu-outlet-psu-map#verification"},{"id":"worksheet-pdu-outlet-to-psu-connection-schedule","title":"Worksheet: PDU outlet-to-PSU connection schedule","canonicalUrl":"https://datacenterlabeling.com/problems/pdu-outlet-psu-map#worksheet-pdu-outlet-to-psu-connection-schedule"},{"id":"faqs","title":"FAQs","canonicalUrl":"https://datacenterlabeling.com/problems/pdu-outlet-psu-map#faqs"}]},{"slug":"grounding-bonding-identification","title":"Grounding and bonding connections cannot be traced","dek":"Connect each conductor and busbar identity to its documented endpoints without confusing identification with electrical integrity.","summary":"Identify a grounding or bonding connection through its conductor, equipment endpoint, busbar identity, and documented termination reference. Compare the physical markers with the relevant drawing and record unresolved relationships. A traceable label identifies the connection; it does not prove electrical continuity, integrity, or compliance. Those conclusions require the applicable technical review.","category":"Power & safety","aliases":["ground earth bond busbar"],"canonicalUrl":"https://datacenterlabeling.com/problems/grounding-bonding-identification","route":"/problems/grounding-bonding-identification","sourceIds":["S03","S41"],"templateIds":["worksheet-14"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking","https://datacenterlabeling.com/problems/operational-versus-safety-labels","https://datacenterlabeling.com/problems/label-audit-evidence"],"markdownUrl":"https://datacenterlabeling.com/problems/grounding-bonding-identification.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/grounding-bonding-identification#quick-answer"},{"id":"when-to-use","title":"When to use","canonicalUrl":"https://datacenterlabeling.com/problems/grounding-bonding-identification#when-to-use"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/grounding-bonding-identification#what-to-gather"},{"id":"identification-workflow","title":"Identification workflow","canonicalUrl":"https://datacenterlabeling.com/problems/grounding-bonding-identification#identification-workflow"},{"id":"start-with-identity-and-scope","title":"Start with identity and scope","canonicalUrl":"https://datacenterlabeling.com/problems/grounding-bonding-identification#start-with-identity-and-scope"},{"id":"build-a-two-endpoint-record-that-can-be-located-again","title":"Build a two-endpoint record that can be located again","canonicalUrl":"https://datacenterlabeling.com/problems/grounding-bonding-identification#build-a-two-endpoint-record-that-can-be-located-again"},{"id":"compare-drawing-field-text-and-aliases-without-overwriting-them","title":"Compare drawing, field text, and aliases without overwriting them","canonicalUrl":"https://datacenterlabeling.com/problems/grounding-bonding-identification#compare-drawing-field-text-and-aliases-without-overwriting-them"},{"id":"worked-case-the-busbar-changed-names-in-one-record-only","title":"Worked case: the busbar changed names in one record only","canonicalUrl":"https://datacenterlabeling.com/problems/grounding-bonding-identification#worked-case-the-busbar-changed-names-in-one-record-only"},{"id":"variations-requiring-a-deliberate-naming-choice","title":"Variations requiring a deliberate naming choice","canonicalUrl":"https://datacenterlabeling.com/problems/grounding-bonding-identification#variations-requiring-a-deliberate-naming-choice"},{"id":"recognize-weak-closure-evidence","title":"Recognize weak closure evidence","canonicalUrl":"https://datacenterlabeling.com/problems/grounding-bonding-identification#recognize-weak-closure-evidence"},{"id":"record-the-project-edition-of-the-bonding-reference","title":"Record the project edition of the bonding reference","canonicalUrl":"https://datacenterlabeling.com/problems/grounding-bonding-identification#record-the-project-edition-of-the-bonding-reference"},{"id":"worked-example","title":"Worked example","canonicalUrl":"https://datacenterlabeling.com/problems/grounding-bonding-identification#worked-example"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/grounding-bonding-identification#common-mistakes"},{"id":"verification","title":"Verification","canonicalUrl":"https://datacenterlabeling.com/problems/grounding-bonding-identification#verification"},{"id":"worksheet-bonding-identification-register","title":"Worksheet: Bonding identification register","canonicalUrl":"https://datacenterlabeling.com/problems/grounding-bonding-identification#worksheet-bonding-identification-register"},{"id":"faqs","title":"FAQs","canonicalUrl":"https://datacenterlabeling.com/problems/grounding-bonding-identification#faqs"}]},{"slug":"operational-versus-safety-labels","title":"Asset stickers and safety labels get mixed up","dek":"Record what each label does, preserve required messages, and route defects to the right owner.","summary":"Distinguish an operational identifier from a manufacturer marking or required safety message before changing labels. Record each label's function, condition, visibility, and approved reference. Preserve required messages and send uncertain safety-marking decisions to the responsible reviewer. Adding an asset sticker does not replace a safety label or establish that the underlying equipment is safe.","category":"Power & safety","aliases":[],"canonicalUrl":"https://datacenterlabeling.com/problems/operational-versus-safety-labels","route":"/problems/operational-versus-safety-labels","sourceIds":["S13","S14","S33","S34"],"templateIds":["worksheet-15","device-label-placement-review","cooling-and-facility-signage-crosswalk","cable-color-legends-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/a-b-power-feed-identification","https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking","https://datacenterlabeling.com/problems/grounding-bonding-identification"],"markdownUrl":"https://datacenterlabeling.com/problems/operational-versus-safety-labels.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/operational-versus-safety-labels#quick-answer"},{"id":"when-to-use","title":"When to use","canonicalUrl":"https://datacenterlabeling.com/problems/operational-versus-safety-labels#when-to-use"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/operational-versus-safety-labels#what-to-gather"},{"id":"identification-workflow","title":"Identification workflow","canonicalUrl":"https://datacenterlabeling.com/problems/operational-versus-safety-labels#identification-workflow"},{"id":"classify-the-label-before-deciding-the-next-action","title":"Classify the label before deciding the next action","canonicalUrl":"https://datacenterlabeling.com/problems/operational-versus-safety-labels#classify-the-label-before-deciding-the-next-action"},{"id":"inventory-the-complete-arrangement","title":"Inventory the complete arrangement","canonicalUrl":"https://datacenterlabeling.com/problems/operational-versus-safety-labels#inventory-the-complete-arrangement"},{"id":"assign-responsibility-at-the-label-entry-level","title":"Assign responsibility at the label-entry level","canonicalUrl":"https://datacenterlabeling.com/problems/operational-versus-safety-labels#assign-responsibility-at-the-label-entry-level"},{"id":"worked-case-a-larger-asset-sticker-covers-a-message","title":"Worked case: a larger asset sticker covers a message","canonicalUrl":"https://datacenterlabeling.com/problems/operational-versus-safety-labels#worked-case-a-larger-asset-sticker-covers-a-message"},{"id":"handle-mixed-and-temporary-information-carefully","title":"Handle mixed and temporary information carefully","canonicalUrl":"https://datacenterlabeling.com/problems/operational-versus-safety-labels#handle-mixed-and-temporary-information-carefully"},{"id":"check-the-full-result-before-closing","title":"Check the full result before closing","canonicalUrl":"https://datacenterlabeling.com/problems/operational-versus-safety-labels#check-the-full-result-before-closing"},{"id":"separate-a-fresh-safety-sticker-from-a-current-technical-reference","title":"Separate a fresh safety sticker from a current technical reference","canonicalUrl":"https://datacenterlabeling.com/problems/operational-versus-safety-labels#separate-a-fresh-safety-sticker-from-a-current-technical-reference"},{"id":"worked-example","title":"Worked example","canonicalUrl":"https://datacenterlabeling.com/problems/operational-versus-safety-labels#worked-example"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/operational-versus-safety-labels#common-mistakes"},{"id":"verification","title":"Verification","canonicalUrl":"https://datacenterlabeling.com/problems/operational-versus-safety-labels#verification"},{"id":"worksheet-safety-label-visibility-and-reference-checklist","title":"Worksheet: Safety-label visibility and reference checklist","canonicalUrl":"https://datacenterlabeling.com/problems/operational-versus-safety-labels#worksheet-safety-label-visibility-and-reference-checklist"},{"id":"faqs","title":"FAQs","canonicalUrl":"https://datacenterlabeling.com/problems/operational-versus-safety-labels#faqs"}]},{"slug":"cooling-pipe-identification","title":"Cooling pipe supply, return, or flow is unclear","dek":"Connect visible pipe markers to the correct fluid system, service role, and documented direction.","summary":"Connect a cooling-pipe marker to the identified system, fluid, documented service role, and direction for that segment. Compare the installed marker with the controlling drawing and record any disagreement. Do not infer flow direction from an ambiguous nearby pipe or transfer a color meaning from another system without the applicable legend and review.","category":"Cooling & facilities","aliases":["chilled water supply return flow pipe"],"canonicalUrl":"https://datacenterlabeling.com/problems/cooling-pipe-identification","route":"/problems/cooling-pipe-identification","sourceIds":["S15"],"templateIds":["worksheet-16","cooling-and-facility-signage-crosswalk"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints","https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk","https://datacenterlabeling.com/problems/label-audit-evidence"],"markdownUrl":"https://datacenterlabeling.com/problems/cooling-pipe-identification.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/cooling-pipe-identification#quick-answer"},{"id":"when-to-use","title":"When to use","canonicalUrl":"https://datacenterlabeling.com/problems/cooling-pipe-identification#when-to-use"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/cooling-pipe-identification#what-to-gather"},{"id":"identification-workflow","title":"Identification workflow","canonicalUrl":"https://datacenterlabeling.com/problems/cooling-pipe-identification#identification-workflow"},{"id":"decide-which-part-of-the-pipe-identity-is-uncertain","title":"Decide which part of the pipe identity is uncertain","canonicalUrl":"https://datacenterlabeling.com/problems/cooling-pipe-identification#decide-which-part-of-the-pipe-identity-is-uncertain"},{"id":"establish-the-system-boundary-and-viewing-reference","title":"Establish the system boundary and viewing reference","canonicalUrl":"https://datacenterlabeling.com/problems/cooling-pipe-identification#establish-the-system-boundary-and-viewing-reference"},{"id":"compare-and-prepare-the-marker-schedule","title":"Compare and prepare the marker schedule","canonicalUrl":"https://datacenterlabeling.com/problems/cooling-pipe-identification#compare-and-prepare-the-marker-schedule"},{"id":"worked-case-the-role-is-wrong-while-the-arrow-agrees","title":"Worked case: the role is wrong while the arrow agrees","canonicalUrl":"https://datacenterlabeling.com/problems/cooling-pipe-identification#worked-case-the-role-is-wrong-while-the-arrow-agrees"},{"id":"variations-to-keep-visible-in-the-register","title":"Variations to keep visible in the register","canonicalUrl":"https://datacenterlabeling.com/problems/cooling-pipe-identification#variations-to-keep-visible-in-the-register"},{"id":"failure-patterns-and-closeout-evidence","title":"Failure patterns and closeout evidence","canonicalUrl":"https://datacenterlabeling.com/problems/cooling-pipe-identification#failure-patterns-and-closeout-evidence"},{"id":"worked-example","title":"Worked example","canonicalUrl":"https://datacenterlabeling.com/problems/cooling-pipe-identification#worked-example"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/cooling-pipe-identification#common-mistakes"},{"id":"verification","title":"Verification","canonicalUrl":"https://datacenterlabeling.com/problems/cooling-pipe-identification#verification"},{"id":"worksheet-cooling-pipe-marker-survey","title":"Worksheet: Cooling pipe-marker survey","canonicalUrl":"https://datacenterlabeling.com/problems/cooling-pipe-identification#worksheet-cooling-pipe-marker-survey"},{"id":"faqs","title":"FAQs","canonicalUrl":"https://datacenterlabeling.com/problems/cooling-pipe-identification#faqs"}]},{"slug":"liquid-cooling-hose-endpoints","title":"Liquid-cooling hoses lose their endpoint identity","dek":"Keep each replaceable hose linked to two exact equipment connections and the correct model-specific reference.","summary":"Give a replaceable liquid-cooling hose a traceable identity and record its two exact equipment connections. Preserve the installed manufacturer's connection names and link the mapping to the correct model-specific diagram. A label review can resolve an identity discrepancy; it does not authorize disconnecting a hose or prove that a routing or fluid arrangement is technically correct.","category":"Cooling & facilities","aliases":["CDU manifold liquid cooling hose"],"canonicalUrl":"https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints","route":"/problems/liquid-cooling-hose-endpoints","sourceIds":["S16"],"templateIds":["worksheet-17","cooling-and-facility-signage-crosswalk"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/cooling-pipe-identification","https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk","https://datacenterlabeling.com/problems/moves-and-retirement-closeout"],"markdownUrl":"https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints#quick-answer"},{"id":"when-to-use","title":"When to use","canonicalUrl":"https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints#when-to-use"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints#what-to-gather"},{"id":"identification-workflow","title":"Identification workflow","canonicalUrl":"https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints#identification-workflow"},{"id":"choose-the-identity-problem-before-changing-the-register","title":"Choose the identity problem before changing the register","canonicalUrl":"https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints#choose-the-identity-problem-before-changing-the-register"},{"id":"establish-configuration-and-preserve-factory-information","title":"Establish configuration and preserve factory information","canonicalUrl":"https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints#establish-configuration-and-preserve-factory-information"},{"id":"describe-the-endpoints-completely","title":"Describe the endpoints completely","canonicalUrl":"https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints#describe-the-endpoints-completely"},{"id":"worked-case-replacement-history-was-attached-to-the-old-hose","title":"Worked case: replacement history was attached to the old hose","canonicalUrl":"https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints#worked-case-replacement-history-was-attached-to-the-old-hose"},{"id":"variations-that-need-explicit-history","title":"Variations that need explicit history","canonicalUrl":"https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints#variations-that-need-explicit-history"},{"id":"failure-patterns-and-closure-checks","title":"Failure patterns and closure checks","canonicalUrl":"https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints#failure-patterns-and-closure-checks"},{"id":"worked-example","title":"Worked example","canonicalUrl":"https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints#worked-example"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints#common-mistakes"},{"id":"verification","title":"Verification","canonicalUrl":"https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints#verification"},{"id":"worksheet-liquid-cooling-hose-connection-register","title":"Worksheet: Liquid-cooling hose connection register","canonicalUrl":"https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints#worksheet-liquid-cooling-hose-connection-register"},{"id":"faqs","title":"FAQs","canonicalUrl":"https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints#faqs"}]},{"slug":"facility-equipment-name-crosswalk","title":"Facility equipment names do not match alarm names","dek":"Link the name seen in an alarm to the physical equipment, drawing, and controlled asset record.","summary":"Link a BMS alarm name to the actual subject it represents before relabeling equipment. A point may refer to a device, sensor, group, or calculated condition rather than a single asset. Record the BMS scope, point reference, physical equipment identity, and drawing relationship, then have the relevant record owners resolve naming conflicts.","category":"Cooling & facilities","aliases":[],"canonicalUrl":"https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk","route":"/problems/facility-equipment-name-crosswalk","sourceIds":["S02","S17","S16"],"templateIds":["worksheet-18","cooling-and-facility-signage-crosswalk"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/asset-versus-location","https://datacenterlabeling.com/problems/cooling-pipe-identification","https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints"],"markdownUrl":"https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk#quick-answer"},{"id":"when-to-use","title":"When to use","canonicalUrl":"https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk#when-to-use"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk#what-to-gather"},{"id":"identification-workflow","title":"Identification workflow","canonicalUrl":"https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk#identification-workflow"},{"id":"decide-whether-the-name-refers-to-equipment-a-point-or-a-group","title":"Decide whether the name refers to equipment, a point, or a group","canonicalUrl":"https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk#decide-whether-the-name-refers-to-equipment-a-point-or-a-group"},{"id":"build-the-record-chain-without-confusing-matching-and-authority","title":"Build the record chain without confusing matching and authority","canonicalUrl":"https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk#build-the-record-chain-without-confusing-matching-and-authority"},{"id":"compare-relationships-in-both-directions","title":"Compare relationships in both directions","canonicalUrl":"https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk#compare-relationships-in-both-directions"},{"id":"worked-case-one-alias-survives-a-physical-unit-replacement","title":"Worked case: one alias survives a physical unit replacement","canonicalUrl":"https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk#worked-case-one-alias-survives-a-physical-unit-replacement"},{"id":"variations-and-failure-patterns","title":"Variations and failure patterns","canonicalUrl":"https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk#variations-and-failure-patterns"},{"id":"evidence-gate-for-publishing-the-crosswalk","title":"Evidence gate for publishing the crosswalk","canonicalUrl":"https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk#evidence-gate-for-publishing-the-crosswalk"},{"id":"resolve-a-leak-zone-alarm-to-its-location-and-associated-cooling-records","title":"Resolve a leak-zone alarm to its location and associated cooling records","canonicalUrl":"https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk#resolve-a-leak-zone-alarm-to-its-location-and-associated-cooling-records"},{"id":"worked-example","title":"Worked example","canonicalUrl":"https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk#worked-example"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk#common-mistakes"},{"id":"verification","title":"Verification","canonicalUrl":"https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk#verification"},{"id":"worksheet-facility-equipment-and-alarm-name-crosswalk","title":"Worksheet: Facility equipment and alarm-name crosswalk","canonicalUrl":"https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk#worksheet-facility-equipment-and-alarm-name-crosswalk"},{"id":"faqs","title":"FAQs","canonicalUrl":"https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk#faqs"}]},{"slug":"pathway-route-identification","title":"Cable pathways cannot be matched to drawings","dek":"Tie each tray, conduit, and penetration reference to a bounded location on the route plan.","summary":"Identify a cable pathway as a bounded physical segment with a matching drawing reference. Record its location, previous and next segments, and any linked cable references needed for the work. Resolve ambiguous tray, conduit, or penetration names against the route plan. A pathway label identifies the route; it does not establish the technical condition of a penetration or its firestopping.","category":"Cooling & facilities","aliases":[],"canonicalUrl":"https://datacenterlabeling.com/problems/pathway-route-identification","route":"/problems/pathway-route-identification","sourceIds":["S01","S18"],"templateIds":["worksheet-19","cooling-and-facility-signage-crosswalk"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/rack-wayfinding","https://datacenterlabeling.com/problems/cable-endpoint-identification","https://datacenterlabeling.com/problems/colocation-demarcation"],"markdownUrl":"https://datacenterlabeling.com/problems/pathway-route-identification.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/pathway-route-identification#quick-answer"},{"id":"when-to-use","title":"When to use","canonicalUrl":"https://datacenterlabeling.com/problems/pathway-route-identification#when-to-use"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/pathway-route-identification#what-to-gather"},{"id":"identification-workflow","title":"Identification workflow","canonicalUrl":"https://datacenterlabeling.com/problems/pathway-route-identification#identification-workflow"},{"id":"decide-whether-the-gap-is-an-object-a-boundary-or-a-relationship","title":"Decide whether the gap is an object, a boundary, or a relationship","canonicalUrl":"https://datacenterlabeling.com/problems/pathway-route-identification#decide-whether-the-gap-is-an-object-a-boundary-or-a-relationship"},{"id":"give-each-segment-repeatable-limits","title":"Give each segment repeatable limits","canonicalUrl":"https://datacenterlabeling.com/problems/pathway-route-identification#give-each-segment-repeatable-limits"},{"id":"match-the-drawing-without-hiding-evidence-limits","title":"Match the drawing without hiding evidence limits","canonicalUrl":"https://datacenterlabeling.com/problems/pathway-route-identification#match-the-drawing-without-hiding-evidence-limits"},{"id":"worked-case-a-branch-inherited-the-main-tray-s-name","title":"Worked case: a branch inherited the main tray's name","canonicalUrl":"https://datacenterlabeling.com/problems/pathway-route-identification#worked-case-a-branch-inherited-the-main-tray-s-name"},{"id":"variations-that-need-careful-relationship-records","title":"Variations that need careful relationship records","canonicalUrl":"https://datacenterlabeling.com/problems/pathway-route-identification#variations-that-need-careful-relationship-records"},{"id":"identify-weak-evidence-and-close-the-precise-finding","title":"Identify weak evidence and close the precise finding","canonicalUrl":"https://datacenterlabeling.com/problems/pathway-route-identification#identify-weak-evidence-and-close-the-precise-finding"},{"id":"keep-floor-coordinates-independent-of-movable-tiles","title":"Keep floor coordinates independent of movable tiles","canonicalUrl":"https://datacenterlabeling.com/problems/pathway-route-identification#keep-floor-coordinates-independent-of-movable-tiles"},{"id":"worked-example","title":"Worked example","canonicalUrl":"https://datacenterlabeling.com/problems/pathway-route-identification#worked-example"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/pathway-route-identification#common-mistakes"},{"id":"verification","title":"Verification","canonicalUrl":"https://datacenterlabeling.com/problems/pathway-route-identification#verification"},{"id":"worksheet-pathway-and-penetration-identification-schedule","title":"Worksheet: Pathway and penetration identification schedule","canonicalUrl":"https://datacenterlabeling.com/problems/pathway-route-identification#worksheet-pathway-and-penetration-identification-schedule"},{"id":"faqs","title":"FAQs","canonicalUrl":"https://datacenterlabeling.com/problems/pathway-route-identification#faqs"}]},{"slug":"colocation-demarcation","title":"Carrier, colo, and tenant circuit IDs disagree","dek":"Preserve each organization's reference while documenting the exact handoff boundary and onward tenant connection.","summary":"Keep provider circuit IDs, colocation cross-connect IDs, and tenant aliases as separate references to the same documented handoff. Record the exact A and Z demarcations, responsibility boundary, and tenant onward patch where applicable. Use the actual provider arrangement and authorization reference; a local crosswalk does not authorize or order a service change.","category":"Cooling & facilities","aliases":["colo cross-connect carrier handoff demarcation"],"canonicalUrl":"https://datacenterlabeling.com/problems/colocation-demarcation","route":"/problems/colocation-demarcation","sourceIds":["S19","S20"],"templateIds":["worksheet-20","labeling-handoff-specification","remote-hands-cabinet-brief"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/rack-wayfinding","https://datacenterlabeling.com/problems/cable-endpoint-identification","https://datacenterlabeling.com/problems/contractor-labeling-handoff"],"markdownUrl":"https://datacenterlabeling.com/problems/colocation-demarcation.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/colocation-demarcation#quick-answer"},{"id":"when-to-use","title":"When to use","canonicalUrl":"https://datacenterlabeling.com/problems/colocation-demarcation#when-to-use"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/colocation-demarcation#what-to-gather"},{"id":"identification-workflow","title":"Identification workflow","canonicalUrl":"https://datacenterlabeling.com/problems/colocation-demarcation#identification-workflow"},{"id":"decide-whether-the-names-differ-or-the-endpoints-disagree","title":"Decide whether the names differ or the endpoints disagree","canonicalUrl":"https://datacenterlabeling.com/problems/colocation-demarcation#decide-whether-the-names-differ-or-the-endpoints-disagree"},{"id":"build-the-source-record-packet","title":"Build the source record packet","canonicalUrl":"https://datacenterlabeling.com/problems/colocation-demarcation#build-the-source-record-packet"},{"id":"separate-provider-delivery-from-the-tenant-s-onward-connection","title":"Separate provider delivery from the tenant's onward connection","canonicalUrl":"https://datacenterlabeling.com/problems/colocation-demarcation#separate-provider-delivery-from-the-tenant-s-onward-connection"},{"id":"worked-case-a-revised-port-is-not-yet-reflected-in-the-loa","title":"Worked case: a revised port is not yet reflected in the LOA","canonicalUrl":"https://datacenterlabeling.com/problems/colocation-demarcation#worked-case-a-revised-port-is-not-yet-reflected-in-the-loa"},{"id":"variations-that-need-more-than-a-renamed-row","title":"Variations that need more than a renamed row","canonicalUrl":"https://datacenterlabeling.com/problems/colocation-demarcation#variations-that-need-more-than-a-renamed-row"},{"id":"failure-patterns-and-evidence-for-closure","title":"Failure patterns and evidence for closure","canonicalUrl":"https://datacenterlabeling.com/problems/colocation-demarcation#failure-patterns-and-evidence-for-closure"},{"id":"worked-example","title":"Worked example","canonicalUrl":"https://datacenterlabeling.com/problems/colocation-demarcation#worked-example"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/colocation-demarcation#common-mistakes"},{"id":"verification","title":"Verification","canonicalUrl":"https://datacenterlabeling.com/problems/colocation-demarcation#verification"},{"id":"worksheet-colocation-demarcation-and-id-crosswalk","title":"Worksheet: Colocation demarcation and ID crosswalk","canonicalUrl":"https://datacenterlabeling.com/problems/colocation-demarcation#worksheet-colocation-demarcation-and-id-crosswalk"},{"id":"faqs","title":"FAQs","canonicalUrl":"https://datacenterlabeling.com/problems/colocation-demarcation#faqs"}]},{"slug":"label-material-failure","title":"Labels peel, fade, or fail in service","dek":"Choose label materials against the surface and exposure they will actually meet, then keep evidence of the sample review.","summary":"Choose a label material as part of a complete application: surface or cable jacket, installation conditions, service exposure, printing combination, and required readable life. Record the failed sample before selecting a replacement. Check the relevant manufacturer evidence and a permitted representative application; a material family name or fresh print appearance does not establish suitability for every installation.","category":"Materials & printing","aliases":["adhesive peeling fade abrasion solvent"],"canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure","route":"/problems/label-material-failure","sourceIds":["S21","S37","S38","S39"],"templateIds":["worksheet-21","site-labeling-standard","labeling-handoff-specification","label-printer-selection-plan","legacy-room-relabeling-planning-template","labeling-business-case-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/dense-rack-label-visibility","https://datacenterlabeling.com/problems/label-fit-and-readability","https://datacenterlabeling.com/problems/label-print-quality"],"markdownUrl":"https://datacenterlabeling.com/problems/label-material-failure.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#quick-answer"},{"id":"when-to-use-this-guide","title":"When to use this guide","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#when-to-use-this-guide"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#what-to-gather"},{"id":"source-context","title":"Source context","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#source-context"},{"id":"suggested-method","title":"Suggested method","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#suggested-method"},{"id":"decide-whether-the-problem-is-identity-attachment-or-print","title":"Decide whether the problem is identity, attachment, or print","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#decide-whether-the-problem-is-identity-attachment-or-print"},{"id":"build-an-application-description-that-a-supplier-can-answer","title":"Build an application description that a supplier can answer","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#build-an-application-description-that-a-supplier-can-answer"},{"id":"compare-candidates-without-changing-the-question-halfway-through","title":"Compare candidates without changing the question halfway through","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#compare-candidates-without-changing-the-question-halfway-through"},{"id":"field-case-a-mixed-preparation-batch","title":"Field case: a mixed preparation batch","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#field-case-a-mixed-preparation-batch"},{"id":"variations-that-change-the-review","title":"Variations that change the review","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#variations-that-change-the-review"},{"id":"failure-patterns-and-the-evidence-needed-to-close-them","title":"Failure patterns and the evidence needed to close them","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#failure-patterns-and-the-evidence-needed-to-close-them"},{"id":"compare-likely-causes-without-treating-clues-as-conclusions","title":"Compare likely causes without treating clues as conclusions","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#compare-likely-causes-without-treating-clues-as-conclusions"},{"id":"write-supplier-questions-that-close-a-specific-gap","title":"Write supplier questions that close a specific gap","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#write-supplier-questions-that-close-a-specific-gap"},{"id":"contain-a-suspect-batch-while-preserving-useful-stock","title":"Contain a suspect batch while preserving useful stock","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#contain-a-suspect-batch-while-preserving-useful-stock"},{"id":"establish-a-meaningful-follow-up-trigger","title":"Establish a meaningful follow-up trigger","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#establish-a-meaningful-follow-up-trigger"},{"id":"read-ul-evidence-and-tamper-claims-at-the-product-level","title":"Read UL evidence and tamper claims at the product level","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#read-ul-evidence-and-tamper-claims-at-the-product-level"},{"id":"worked-example-fictional","title":"Worked example (fictional)","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#worked-example-fictional"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#common-mistakes"},{"id":"verification-checklist","title":"Verification checklist","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#verification-checklist"},{"id":"worksheet-field-dictionary","title":"Worksheet field dictionary","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#worksheet-field-dictionary"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/problems/label-material-failure#frequently-asked-questions"}]},{"slug":"label-fit-and-readability","title":"The label does not fit or the text is too small","dek":"Balance usable print space, cable geometry, and installed access without shortening the identifier into ambiguity.","summary":"Choose label dimensions from the actual object geometry, usable print area, approved text, and installed access. Evaluate the proposed format at its real size with the longest required identifier. If the label does not fit, review layout or format before shortening identity. Keep the termination state and applicable material instructions in the decision.","category":"Materials & printing","aliases":[],"canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability","route":"/problems/label-fit-and-readability","sourceIds":["S08","S21"],"templateIds":["worksheet-22","patch-panel-print-proof","fiber-assembly-reference-record","device-label-placement-review","label-printer-selection-plan","cable-color-legends-planning-template","labeling-business-case-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/naming-convention","https://datacenterlabeling.com/problems/dense-rack-label-visibility","https://datacenterlabeling.com/problems/label-material-failure"],"markdownUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#quick-answer"},{"id":"when-to-use-this-guide","title":"When to use this guide","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#when-to-use-this-guide"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#what-to-gather"},{"id":"source-context","title":"Source context","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#source-context"},{"id":"suggested-method","title":"Suggested method","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#suggested-method"},{"id":"separate-missing-space-from-an-unclear-reading-task","title":"Separate missing space from an unclear reading task","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#separate-missing-space-from-an-unclear-reading-task"},{"id":"measure-the-whole-placement-not-just-the-stock","title":"Measure the whole placement, not just the stock","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#measure-the-whole-placement-not-just-the-stock"},{"id":"design-a-legend-around-decisions-the-reader-must-make","title":"Design a legend around decisions the reader must make","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#design-a-legend-around-decisions-the-reader-must-make"},{"id":"read-and-handle-the-applied-proof-as-it-will-be-used","title":"Read and handle the applied proof as it will be used","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#read-and-handle-the-applied-proof-as-it-will-be-used"},{"id":"field-case-a-readable-marker-hides-its-neighbor","title":"Field case: a readable marker hides its neighbor","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#field-case-a-readable-marker-hides-its-neighbor"},{"id":"handle-different-object-types-deliberately","title":"Handle different object types deliberately","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#handle-different-object-types-deliberately"},{"id":"acceptance-evidence-that-survives-a-reprint","title":"Acceptance evidence that survives a reprint","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#acceptance-evidence-that-survives-a-reprint"},{"id":"compare-formats-against-the-same-reading-problem","title":"Compare formats against the same reading problem","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#compare-formats-against-the-same-reading-problem"},{"id":"build-a-proof-population-rather-than-one-attractive-sample","title":"Build a proof population rather than one attractive sample","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#build-a-proof-population-rather-than-one-attractive-sample"},{"id":"field-case-a-new-description-exceeds-the-accepted-layout","title":"Field case: a new description exceeds the accepted layout","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#field-case-a-new-description-exceeds-the-accepted-layout"},{"id":"distinguish-fit-approval-from-production-and-installation-checks","title":"Distinguish fit approval from production and installation checks","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#distinguish-fit-approval-from-production-and-installation-checks"},{"id":"worked-example-fictional","title":"Worked example (fictional)","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#worked-example-fictional"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#common-mistakes"},{"id":"verification-checklist","title":"Verification checklist","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#verification-checklist"},{"id":"worksheet-field-dictionary","title":"Worksheet field dictionary","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#worksheet-field-dictionary"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/problems/label-fit-and-readability#frequently-asked-questions"}]},{"slug":"label-print-quality","title":"Print smears, clips, or shifts","dek":"Diagnose the physical output with a controlled proof so a correct source file becomes a readable installed label.","summary":"Diagnose print smearing, clipping, or drift with a controlled proof tied to the exact printer, template, media, ribbon, and settings. First confirm that the source content is correct, then change one relevant cause at a time using the applicable instructions. Keep accepted and rejected samples so the corrected setup can be reproduced.","category":"Materials & printing","aliases":[],"canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality","route":"/problems/label-print-quality","sourceIds":["S22","S23"],"templateIds":["worksheet-23","patch-panel-print-proof","label-printer-selection-plan","labeling-business-case-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/patch-panel-port-mapping","https://datacenterlabeling.com/problems/label-material-failure","https://datacenterlabeling.com/problems/barcode-qr-scan-quality"],"markdownUrl":"https://datacenterlabeling.com/problems/label-print-quality.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality#quick-answer"},{"id":"when-to-use-this-guide","title":"When to use this guide","canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality#when-to-use-this-guide"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality#what-to-gather"},{"id":"source-context","title":"Source context","canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality#source-context"},{"id":"suggested-method","title":"Suggested method","canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality#suggested-method"},{"id":"find-the-first-stage-where-the-output-becomes-wrong","title":"Find the first stage where the output becomes wrong","canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality#find-the-first-stage-where-the-output-becomes-wrong"},{"id":"establish-a-reproducible-starting-condition","title":"Establish a reproducible starting condition","canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality#establish-a-reproducible-starting-condition"},{"id":"branch-a-content-clips-or-wraps-unexpectedly","title":"Branch A: content clips or wraps unexpectedly","canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality#branch-a-content-clips-or-wraps-unexpectedly"},{"id":"branch-b-placement-changes-through-the-run","title":"Branch B: placement changes through the run","canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality#branch-b-placement-changes-through-the-run"},{"id":"branch-c-weak-print-streaks-or-unstable-characters","title":"Branch C: weak print, streaks, or unstable characters","canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality#branch-c-weak-print-streaks-or-unstable-characters"},{"id":"field-case-drift-appears-after-a-media-reload","title":"Field case: drift appears after a media reload","canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality#field-case-drift-appears-after-a-media-reload"},{"id":"compare-application-paths-when-one-workstation-prints-differently","title":"Compare application paths when one workstation prints differently","canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality#compare-application-paths-when-one-workstation-prints-differently"},{"id":"control-interruptions-supplies-and-uncertain-output","title":"Control interruptions, supplies, and uncertain output","canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality#control-interruptions-supplies-and-uncertain-output"},{"id":"what-a-complete-release-packet-contains","title":"What a complete release packet contains","canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality#what-a-complete-release-packet-contains"},{"id":"keep-printer-diagnosis-separate-from-installation-acceptance","title":"Keep printer diagnosis separate from installation acceptance","canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality#keep-printer-diagnosis-separate-from-installation-acceptance"},{"id":"worked-example-fictional","title":"Worked example (fictional)","canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality#worked-example-fictional"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality#common-mistakes"},{"id":"verification-checklist","title":"Verification checklist","canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality#verification-checklist"},{"id":"worksheet-field-dictionary","title":"Worksheet field dictionary","canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality#worksheet-field-dictionary"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/problems/label-print-quality#frequently-asked-questions"}]},{"slug":"bulk-label-import","title":"Bulk imports corrupt or duplicate identifiers","dek":"Protect exact identifier text and reconcile label quantities before a spreadsheet becomes a large print batch.","summary":"Treat identifiers as exact text through export, import, preview, and printing. Compare the approved source with the actual preview, including leading zeros, endpoint fields, ordering, and copy counts. Record the released source and template revisions, then account for accepted output, rejects, and authorized reprints. An imported row count alone does not prove that the labels are correct.","category":"Materials & printing","aliases":[],"canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import","route":"/problems/bulk-label-import","sourceIds":["S24","S49"],"templateIds":["worksheet-24","patch-panel-print-proof","panel-port-relationship-schedule","label-printer-selection-plan","legacy-room-relabeling-planning-template","labeling-business-case-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/duplicate-identifiers","https://datacenterlabeling.com/problems/gpu-cable-staging","https://datacenterlabeling.com/problems/label-print-quality"],"markdownUrl":"https://datacenterlabeling.com/problems/bulk-label-import.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import#quick-answer"},{"id":"when-to-use-this-guide","title":"When to use this guide","canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import#when-to-use-this-guide"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import#what-to-gather"},{"id":"source-context","title":"Source context","canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import#source-context"},{"id":"suggested-method","title":"Suggested method","canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import#suggested-method"},{"id":"decide-what-is-duplicated-before-deleting-anything","title":"Decide what is duplicated before deleting anything","canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import#decide-what-is-duplicated-before-deleting-anything"},{"id":"keep-a-received-source-and-a-controlled-preparation-copy","title":"Keep a received source and a controlled preparation copy","canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import#keep-a-received-source-and-a-controlled-preparation-copy"},{"id":"treat-an-identifier-as-an-exact-string","title":"Treat an identifier as an exact string","canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import#treat-an-identifier-as-an-exact-string"},{"id":"validate-relationships-across-fields","title":"Validate relationships across fields","canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import#validate-relationships-across-fields"},{"id":"field-case-sorting-breaks-endpoint-relationships","title":"Field case: sorting breaks endpoint relationships","canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import#field-case-sorting-breaks-endpoint-relationships"},{"id":"count-objects-faces-and-physical-output-separately","title":"Count objects, faces, and physical output separately","canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import#count-objects-faces-and-physical-output-separately"},{"id":"control-cut-and-feed-choices-without-losing-cable-label-pairs","title":"Control cut and feed choices without losing cable-label pairs","canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import#control-cut-and-feed-choices-without-losing-cable-label-pairs"},{"id":"compare-three-plausible-remedies","title":"Compare three plausible remedies","canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import#compare-three-plausible-remedies"},{"id":"release-a-package-another-shift-can-reproduce","title":"Release a package another shift can reproduce","canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import#release-a-package-another-shift-can-reproduce"},{"id":"retain-evidence-of-intentional-transformations","title":"Retain evidence of intentional transformations","canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import#retain-evidence-of-intentional-transformations"},{"id":"worked-example-fictional","title":"Worked example (fictional)","canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import#worked-example-fictional"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import#common-mistakes"},{"id":"verification-checklist","title":"Verification checklist","canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import#verification-checklist"},{"id":"worksheet-field-dictionary","title":"Worksheet field dictionary","canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import#worksheet-field-dictionary"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/problems/bulk-label-import#frequently-asked-questions"}]},{"slug":"barcode-qr-scan-quality","title":"A barcode or QR code will not scan reliably","dek":"Check whether the symbol decodes, what text it returns, and whether that text leads to the intended record.","summary":"Check a barcode or QR workflow in three stages: whether the symbol decodes, whether the returned text matches the expected payload, and whether that payload reaches the intended record. Test the installed label with the actual supported reader and profile. A successful beep does not prove correct identity or record access, and a working phone does not qualify every scanner.","category":"Materials & printing","aliases":["QR barcode scan data matrix"],"canonicalUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality","route":"/problems/barcode-qr-scan-quality","sourceIds":["S25"],"templateIds":["worksheet-25","device-label-placement-review","label-printer-selection-plan","identification-technology-pilot-plan"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/asset-versus-location","https://datacenterlabeling.com/problems/label-print-quality","https://datacenterlabeling.com/problems/label-record-reconciliation"],"markdownUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality#quick-answer"},{"id":"when-to-use-this-guide","title":"When to use this guide","canonicalUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality#when-to-use-this-guide"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality#what-to-gather"},{"id":"source-context","title":"Source context","canonicalUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality#source-context"},{"id":"suggested-method","title":"Suggested method","canonicalUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality#suggested-method"},{"id":"separate-four-outcomes-that-can-sound-like-one-failure","title":"Separate four outcomes that can sound like one failure","canonicalUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality#separate-four-outcomes-that-can-sound-like-one-failure"},{"id":"define-exactly-what-the-code-is-meant-to-carry","title":"Define exactly what the code is meant to carry","canonicalUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality#define-exactly-what-the-code-is-meant-to-carry"},{"id":"diagnose-a-symbol-that-does-not-decode","title":"Diagnose a symbol that does not decode","canonicalUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality#diagnose-a-symbol-that-does-not-decode"},{"id":"diagnose-correct-decoding-with-incorrect-returned-text","title":"Diagnose correct decoding with incorrect returned text","canonicalUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality#diagnose-correct-decoding-with-incorrect-returned-text"},{"id":"diagnose-a-correct-payload-that-reaches-the-wrong-place","title":"Diagnose a correct payload that reaches the wrong place","canonicalUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality#diagnose-a-correct-payload-that-reaches-the-wrong-place"},{"id":"field-case-a-good-desk-proof-fails-in-a-crowded-installed-view","title":"Field case: a good desk proof fails in a crowded installed view","canonicalUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality#field-case-a-good-desk-proof-fails-in-a-crowded-installed-view"},{"id":"variations-for-curved-labels-multiple-devices-and-offline-work","title":"Variations for curved labels, multiple devices, and offline work","canonicalUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality#variations-for-curved-labels-multiple-devices-and-offline-work"},{"id":"make-the-test-result-useful-for-later-failures","title":"Make the test result useful for later failures","canonicalUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality#make-the-test-result-useful-for-later-failures"},{"id":"keep-label-identity-distinct-from-application-availability","title":"Keep label identity distinct from application availability","canonicalUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality#keep-label-identity-distinct-from-application-availability"},{"id":"worked-example-fictional","title":"Worked example (fictional)","canonicalUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality#worked-example-fictional"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality#common-mistakes"},{"id":"verification-checklist","title":"Verification checklist","canonicalUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality#verification-checklist"},{"id":"worksheet-field-dictionary","title":"Worksheet field dictionary","canonicalUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality#worksheet-field-dictionary"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/problems/barcode-qr-scan-quality#frequently-asked-questions"}]},{"slug":"label-record-reconciliation","title":"The physical label and system record disagree","dek":"Resolve each conflicting field with an identified owner and evidence, preserving the difference between observation and approval.","summary":"Resolve a label-to-record mismatch field by field. Preserve the observed label and each system's value, identify the owner with authority over the disputed field, and record the evidence behind the approved correction. Keep observations separate from confirmed facts. Close the physical label, affected records, and retained history together rather than selecting whichever value is easiest to edit.","category":"Records & lifecycle","aliases":["DCIM CMDB inventory asset database"],"canonicalUrl":"https://datacenterlabeling.com/problems/label-record-reconciliation","route":"/problems/label-record-reconciliation","sourceIds":["S02","S35","S36"],"templateIds":["worksheet-26","change-ticket-labeling-closeout","remote-hands-cabinet-brief","panel-port-relationship-schedule","identification-technology-pilot-plan","legacy-room-relabeling-planning-template","labeling-business-case-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/asset-versus-location","https://datacenterlabeling.com/problems/cable-endpoint-identification","https://datacenterlabeling.com/problems/moves-and-retirement-closeout"],"markdownUrl":"https://datacenterlabeling.com/problems/label-record-reconciliation.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/label-record-reconciliation#quick-answer"},{"id":"when-to-use-this-guide","title":"When to use this guide","canonicalUrl":"https://datacenterlabeling.com/problems/label-record-reconciliation#when-to-use-this-guide"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/label-record-reconciliation#what-to-gather"},{"id":"source-context","title":"Source context","canonicalUrl":"https://datacenterlabeling.com/problems/label-record-reconciliation#source-context"},{"id":"suggested-method","title":"Suggested method","canonicalUrl":"https://datacenterlabeling.com/problems/label-record-reconciliation#suggested-method"},{"id":"resolve-identity-before-choosing-a-winning-value","title":"Resolve identity before choosing a winning value","canonicalUrl":"https://datacenterlabeling.com/problems/label-record-reconciliation#resolve-identity-before-choosing-a-winning-value"},{"id":"capture-the-disagreement-without-destroying-its-history","title":"Capture the disagreement without destroying its history","canonicalUrl":"https://datacenterlabeling.com/problems/label-record-reconciliation#capture-the-disagreement-without-destroying-its-history"},{"id":"decide-the-correction-at-field-level","title":"Decide the correction at field level","canonicalUrl":"https://datacenterlabeling.com/problems/label-record-reconciliation#decide-the-correction-at-field-level"},{"id":"field-case-a-corrected-value-returns-to-its-old-state","title":"Field case: a corrected value returns to its old state","canonicalUrl":"https://datacenterlabeling.com/problems/label-record-reconciliation#field-case-a-corrected-value-returns-to-its-old-state"},{"id":"variations-for-connections-rack-occupancy-and-aliases","title":"Variations for connections, rack occupancy, and aliases","canonicalUrl":"https://datacenterlabeling.com/problems/label-record-reconciliation#variations-for-connections-rack-occupancy-and-aliases"},{"id":"avoid-a-tidy-register-with-unfinished-corrections","title":"Avoid a tidy register with unfinished corrections","canonicalUrl":"https://datacenterlabeling.com/problems/label-record-reconciliation#avoid-a-tidy-register-with-unfinished-corrections"},{"id":"make-a-dcim-export-repeatable-before-using-it-as-label-evidence","title":"Make a DCIM export repeatable before using it as label evidence","canonicalUrl":"https://datacenterlabeling.com/problems/label-record-reconciliation#make-a-dcim-export-repeatable-before-using-it-as-label-evidence"},{"id":"worked-example-fictional","title":"Worked example (fictional)","canonicalUrl":"https://datacenterlabeling.com/problems/label-record-reconciliation#worked-example-fictional"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/label-record-reconciliation#common-mistakes"},{"id":"verification-checklist","title":"Verification checklist","canonicalUrl":"https://datacenterlabeling.com/problems/label-record-reconciliation#verification-checklist"},{"id":"worksheet-field-dictionary","title":"Worksheet field dictionary","canonicalUrl":"https://datacenterlabeling.com/problems/label-record-reconciliation#worksheet-field-dictionary"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/problems/label-record-reconciliation#frequently-asked-questions"}]},{"slug":"cable-test-id-reconciliation","title":"Test results use different cable IDs","dek":"Connect each installed label to the original test record without turning an unexplained rename into proof.","summary":"Link the applied cable label to the original test-result identifier and the verified endpoints. Preserve the original result and document the identity crosswalk instead of silently renaming it. Resolving the cable's identity and accepting its technical result are separate decisions; keep both statuses visible until the responsible reviewers close them.","category":"Records & lifecycle","aliases":[],"canonicalUrl":"https://datacenterlabeling.com/problems/cable-test-id-reconciliation","route":"/problems/cable-test-id-reconciliation","sourceIds":["S26"],"templateIds":["worksheet-27","labeling-handoff-specification","fiber-assembly-reference-record"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/cable-endpoint-identification","https://datacenterlabeling.com/problems/bulk-label-import","https://datacenterlabeling.com/problems/contractor-labeling-handoff"],"markdownUrl":"https://datacenterlabeling.com/problems/cable-test-id-reconciliation.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/cable-test-id-reconciliation#quick-answer"},{"id":"when-to-use-this-guide","title":"When to use this guide","canonicalUrl":"https://datacenterlabeling.com/problems/cable-test-id-reconciliation#when-to-use-this-guide"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/cable-test-id-reconciliation#what-to-gather"},{"id":"source-context","title":"Source context","canonicalUrl":"https://datacenterlabeling.com/problems/cable-test-id-reconciliation#source-context"},{"id":"suggested-method","title":"Suggested method","canonicalUrl":"https://datacenterlabeling.com/problems/cable-test-id-reconciliation#suggested-method"},{"id":"decide-which-evidence-is-missing","title":"Decide which evidence is missing","canonicalUrl":"https://datacenterlabeling.com/problems/cable-test-id-reconciliation#decide-which-evidence-is-missing"},{"id":"preserve-the-received-evidence-and-its-internal-names","title":"Preserve the received evidence and its internal names","canonicalUrl":"https://datacenterlabeling.com/problems/cable-test-id-reconciliation#preserve-the-received-evidence-and-its-internal-names"},{"id":"build-a-defensible-correspondence","title":"Build a defensible correspondence","canonicalUrl":"https://datacenterlabeling.com/problems/cable-test-id-reconciliation#build-a-defensible-correspondence"},{"id":"field-case-identical-temporary-names-in-two-sessions","title":"Field case: identical temporary names in two sessions","canonicalUrl":"https://datacenterlabeling.com/problems/cable-test-id-reconciliation#field-case-identical-temporary-names-in-two-sessions"},{"id":"handle-retests-and-revised-reports-without-losing-chronology","title":"Handle retests and revised reports without losing chronology","canonicalUrl":"https://datacenterlabeling.com/problems/cable-test-id-reconciliation#handle-retests-and-revised-reports-without-losing-chronology"},{"id":"close-identity-and-technical-review-separately","title":"Close identity and technical review separately","canonicalUrl":"https://datacenterlabeling.com/problems/cable-test-id-reconciliation#close-identity-and-technical-review-separately"},{"id":"worked-example-fictional","title":"Worked example (fictional)","canonicalUrl":"https://datacenterlabeling.com/problems/cable-test-id-reconciliation#worked-example-fictional"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/cable-test-id-reconciliation#common-mistakes"},{"id":"verification-checklist","title":"Verification checklist","canonicalUrl":"https://datacenterlabeling.com/problems/cable-test-id-reconciliation#verification-checklist"},{"id":"worksheet-field-dictionary","title":"Worksheet field dictionary","canonicalUrl":"https://datacenterlabeling.com/problems/cable-test-id-reconciliation#worksheet-field-dictionary"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/problems/cable-test-id-reconciliation#frequently-asked-questions"}]},{"slug":"contractor-labeling-handoff","title":"Contractor handoffs leave inconsistent labels","dek":"Turn the delivered label schedule, as-builts, and test package into a handoff that operations can actually use.","summary":"Accept a contractor labeling package by checking the installed identifiers against the released schedule, governing policy revision, as-built records, and test index. Define the delivered scope and retain exceptions with an owner and disposition. A set of tidy labels or a complete file list is not enough if operations cannot reconcile those files with the installed objects.","category":"Records & lifecycle","aliases":[],"canonicalUrl":"https://datacenterlabeling.com/problems/contractor-labeling-handoff","route":"/problems/contractor-labeling-handoff","sourceIds":["S18"],"templateIds":["worksheet-28","site-labeling-standard","labeling-handoff-specification","remote-hands-cabinet-brief","label-printer-selection-plan","identification-technology-pilot-plan","legacy-room-relabeling-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/naming-convention","https://datacenterlabeling.com/problems/colocation-demarcation","https://datacenterlabeling.com/problems/cable-test-id-reconciliation"],"markdownUrl":"https://datacenterlabeling.com/problems/contractor-labeling-handoff.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/contractor-labeling-handoff#quick-answer"},{"id":"when-to-use-this-guide","title":"When to use this guide","canonicalUrl":"https://datacenterlabeling.com/problems/contractor-labeling-handoff#when-to-use-this-guide"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/contractor-labeling-handoff#what-to-gather"},{"id":"source-context","title":"Source context","canonicalUrl":"https://datacenterlabeling.com/problems/contractor-labeling-handoff#source-context"},{"id":"suggested-method","title":"Suggested method","canonicalUrl":"https://datacenterlabeling.com/problems/contractor-labeling-handoff#suggested-method"},{"id":"decide-whether-you-are-reviewing-a-deliverable-or-accepting-work","title":"Decide whether you are reviewing a deliverable or accepting work","canonicalUrl":"https://datacenterlabeling.com/problems/contractor-labeling-handoff#decide-whether-you-are-reviewing-a-deliverable-or-accepting-work"},{"id":"agree-a-useful-deliverable-index-before-rollout","title":"Agree a useful deliverable index before rollout","canonicalUrl":"https://datacenterlabeling.com/problems/contractor-labeling-handoff#agree-a-useful-deliverable-index-before-rollout"},{"id":"check-the-package-in-both-directions","title":"Check the package in both directions","canonicalUrl":"https://datacenterlabeling.com/problems/contractor-labeling-handoff#check-the-package-in-both-directions"},{"id":"field-case-a-later-schedule-loses-an-approved-deviation","title":"Field case: a later schedule loses an approved deviation","canonicalUrl":"https://datacenterlabeling.com/problems/contractor-labeling-handoff#field-case-a-later-schedule-loses-an-approved-deviation"},{"id":"write-punch-items-that-can-actually-be-verified","title":"Write punch items that can actually be verified","canonicalUrl":"https://datacenterlabeling.com/problems/contractor-labeling-handoff#write-punch-items-that-can-actually-be-verified"},{"id":"manage-partial-packages-and-interfaces-deliberately","title":"Manage partial packages and interfaces deliberately","canonicalUrl":"https://datacenterlabeling.com/problems/contractor-labeling-handoff#manage-partial-packages-and-interfaces-deliberately"},{"id":"close-with-a-coherent-current-record-set","title":"Close with a coherent current record set","canonicalUrl":"https://datacenterlabeling.com/problems/contractor-labeling-handoff#close-with-a-coherent-current-record-set"},{"id":"write-deliverable-requirements-that-name-the-evidence-of-completion","title":"Write deliverable requirements that name the evidence of completion","canonicalUrl":"https://datacenterlabeling.com/problems/contractor-labeling-handoff#write-deliverable-requirements-that-name-the-evidence-of-completion"},{"id":"worked-example-fictional","title":"Worked example (fictional)","canonicalUrl":"https://datacenterlabeling.com/problems/contractor-labeling-handoff#worked-example-fictional"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/contractor-labeling-handoff#common-mistakes"},{"id":"verification-checklist","title":"Verification checklist","canonicalUrl":"https://datacenterlabeling.com/problems/contractor-labeling-handoff#verification-checklist"},{"id":"worksheet-field-dictionary","title":"Worksheet field dictionary","canonicalUrl":"https://datacenterlabeling.com/problems/contractor-labeling-handoff#worksheet-field-dictionary"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/problems/contractor-labeling-handoff#frequently-asked-questions"}]},{"slug":"moves-and-retirement-closeout","title":"Moves and retirements leave stale labels behind","dek":"Choose a change, migration, or retirement path and close physical identification and records together.","summary":"Choose the correct closeout path for a move, addition, replacement, migration, or retirement. Record the old and final states, account for physical labels, and update the related asset, location, and connection records. Preserve the history needed to interpret earlier work. A retired database status alone does not establish what remains physically installed.","category":"Records & lifecycle","aliases":["decommission retire change move migrate"],"canonicalUrl":"https://datacenterlabeling.com/problems/moves-and-retirement-closeout","route":"/problems/moves-and-retirement-closeout","sourceIds":["S27","S28","S40"],"templateIds":["worksheet-29","site-labeling-standard","change-ticket-labeling-closeout","identification-technology-pilot-plan","legacy-room-relabeling-planning-template","labeling-business-case-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/asset-versus-location","https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints","https://datacenterlabeling.com/problems/label-record-reconciliation"],"markdownUrl":"https://datacenterlabeling.com/problems/moves-and-retirement-closeout.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/moves-and-retirement-closeout#quick-answer"},{"id":"when-to-use-this-guide","title":"When to use this guide","canonicalUrl":"https://datacenterlabeling.com/problems/moves-and-retirement-closeout#when-to-use-this-guide"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/moves-and-retirement-closeout#what-to-gather"},{"id":"source-context","title":"Source context","canonicalUrl":"https://datacenterlabeling.com/problems/moves-and-retirement-closeout#source-context"},{"id":"suggested-method","title":"Suggested method","canonicalUrl":"https://datacenterlabeling.com/problems/moves-and-retirement-closeout#suggested-method"},{"id":"choose-the-path-from-the-actual-transition","title":"Choose the path from the actual transition","canonicalUrl":"https://datacenterlabeling.com/problems/moves-and-retirement-closeout#choose-the-path-from-the-actual-transition"},{"id":"build-an-affected-label-list-before-closeout","title":"Build an affected-label list before closeout","canonicalUrl":"https://datacenterlabeling.com/problems/moves-and-retirement-closeout#build-an-affected-label-list-before-closeout"},{"id":"close-a-move-or-connection-change","title":"Close a move or connection change","canonicalUrl":"https://datacenterlabeling.com/problems/moves-and-retirement-closeout#close-a-move-or-connection-change"},{"id":"reconcile-migration-by-object-and-event","title":"Reconcile migration by object and event","canonicalUrl":"https://datacenterlabeling.com/problems/moves-and-retirement-closeout#reconcile-migration-by-object-and-event"},{"id":"field-case-a-deferred-object-stays-visible-across-waves","title":"Field case: a deferred object stays visible across waves","canonicalUrl":"https://datacenterlabeling.com/problems/moves-and-retirement-closeout#field-case-a-deferred-object-stays-visible-across-waves"},{"id":"preserve-identity-through-retirement","title":"Preserve identity through retirement","canonicalUrl":"https://datacenterlabeling.com/problems/moves-and-retirement-closeout#preserve-identity-through-retirement"},{"id":"handle-rollback-substitution-and-partial-completion","title":"Handle rollback, substitution, and partial completion","canonicalUrl":"https://datacenterlabeling.com/problems/moves-and-retirement-closeout#handle-rollback-substitution-and-partial-completion"},{"id":"incident-context-cloudflare-cabinet-retirement-in-april-2020","title":"Incident context: Cloudflare cabinet retirement in April 2020","canonicalUrl":"https://datacenterlabeling.com/problems/moves-and-retirement-closeout#incident-context-cloudflare-cabinet-retirement-in-april-2020"},{"id":"worked-example-fictional","title":"Worked example (fictional)","canonicalUrl":"https://datacenterlabeling.com/problems/moves-and-retirement-closeout#worked-example-fictional"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/moves-and-retirement-closeout#common-mistakes"},{"id":"verification-checklist","title":"Verification checklist","canonicalUrl":"https://datacenterlabeling.com/problems/moves-and-retirement-closeout#verification-checklist"},{"id":"worksheet-field-dictionary","title":"Worksheet field dictionary","canonicalUrl":"https://datacenterlabeling.com/problems/moves-and-retirement-closeout#worksheet-field-dictionary"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/problems/moves-and-retirement-closeout#frequently-asked-questions"}]},{"slug":"label-audit-evidence","title":"No one can prove labels were checked","dek":"Make the audit scope, observed defects, decisions, and closure evidence visible enough for another reviewer to follow.","summary":"Define the label audit's population, criteria, and evidence before inspecting objects. Record the actual observation, decision, correction, owner, and closure for each finding. Keep the sample selection reproducible and state which objects were outside the review. A completed checklist supports only its documented scope; it is not proof that every label in the facility was checked.","category":"Records & lifecycle","aliases":[],"canonicalUrl":"https://datacenterlabeling.com/problems/label-audit-evidence","route":"/problems/label-audit-evidence","sourceIds":["S29"],"templateIds":["worksheet-30","labeling-handoff-specification","label-printer-selection-plan","identification-technology-pilot-plan","legacy-room-relabeling-planning-template","labeling-business-case-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/grounding-bonding-identification","https://datacenterlabeling.com/problems/label-material-failure","https://datacenterlabeling.com/problems/label-record-reconciliation"],"markdownUrl":"https://datacenterlabeling.com/problems/label-audit-evidence.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/problems/label-audit-evidence#quick-answer"},{"id":"when-to-use-this-guide","title":"When to use this guide","canonicalUrl":"https://datacenterlabeling.com/problems/label-audit-evidence#when-to-use-this-guide"},{"id":"what-to-gather","title":"What to gather","canonicalUrl":"https://datacenterlabeling.com/problems/label-audit-evidence#what-to-gather"},{"id":"source-context","title":"Source context","canonicalUrl":"https://datacenterlabeling.com/problems/label-audit-evidence#source-context"},{"id":"suggested-method","title":"Suggested method","canonicalUrl":"https://datacenterlabeling.com/problems/label-audit-evidence#suggested-method"},{"id":"define-the-claim-before-walking-the-floor","title":"Define the claim before walking the floor","canonicalUrl":"https://datacenterlabeling.com/problems/label-audit-evidence#define-the-claim-before-walking-the-floor"},{"id":"make-sample-selection-reproducible","title":"Make sample selection reproducible","canonicalUrl":"https://datacenterlabeling.com/problems/label-audit-evidence#make-sample-selection-reproducible"},{"id":"record-the-observation-before-deciding-the-remedy","title":"Record the observation before deciding the remedy","canonicalUrl":"https://datacenterlabeling.com/problems/label-audit-evidence#record-the-observation-before-deciding-the-remedy"},{"id":"turn-each-defect-into-a-verifiable-assignment","title":"Turn each defect into a verifiable assignment","canonicalUrl":"https://datacenterlabeling.com/problems/label-audit-evidence#turn-each-defect-into-a-verifiable-assignment"},{"id":"field-case-one-object-has-two-different-criterion-outcomes","title":"Field case: one object has two different criterion outcomes","canonicalUrl":"https://datacenterlabeling.com/problems/label-audit-evidence#field-case-one-object-has-two-different-criterion-outcomes"},{"id":"reconcile-counts-without-concealing-exceptions","title":"Reconcile counts without concealing exceptions","canonicalUrl":"https://datacenterlabeling.com/problems/label-audit-evidence#reconcile-counts-without-concealing-exceptions"},{"id":"review-closure-as-a-separate-observation","title":"Review closure as a separate observation","canonicalUrl":"https://datacenterlabeling.com/problems/label-audit-evidence#review-closure-as-a-separate-observation"},{"id":"worked-example-fictional","title":"Worked example (fictional)","canonicalUrl":"https://datacenterlabeling.com/problems/label-audit-evidence#worked-example-fictional"},{"id":"common-mistakes","title":"Common mistakes","canonicalUrl":"https://datacenterlabeling.com/problems/label-audit-evidence#common-mistakes"},{"id":"verification-checklist","title":"Verification checklist","canonicalUrl":"https://datacenterlabeling.com/problems/label-audit-evidence#verification-checklist"},{"id":"worksheet-field-dictionary","title":"Worksheet field dictionary","canonicalUrl":"https://datacenterlabeling.com/problems/label-audit-evidence#worksheet-field-dictionary"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/problems/label-audit-evidence#frequently-asked-questions"}]},{"slug":"choosing-a-label-printer","title":"Choose a label printer for the work you actually do","dek":"Compare portable and desktop workflows, qualify the exact materials and software, and calculate cost from accepted labels before selecting a printer.","summary":"Choose a label printer by testing the actual workload, required formats, approved data path, and exact media and ribbon combination. Use representative imports, endpoint pairs, interruptions, and replacements to check reproducible output. Compare costs using accepted labels or complete sets, with hardware and labor stated separately. Keep material evidence, software access, support, and unresolved requirements in the selection record.","category":"Planning & decisions","canonicalUrl":"https://datacenterlabeling.com/guides/choosing-a-label-printer","route":"/guides/choosing-a-label-printer","sourceIds":["S42","S22"],"templateIds":["label-printer-selection-plan"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/cable-endpoint-identification","https://datacenterlabeling.com/problems/patch-panel-port-mapping","https://datacenterlabeling.com/problems/label-material-failure","https://datacenterlabeling.com/problems/label-fit-and-readability","https://datacenterlabeling.com/problems/label-print-quality","https://datacenterlabeling.com/problems/bulk-label-import","https://datacenterlabeling.com/problems/barcode-qr-scan-quality","https://datacenterlabeling.com/problems/contractor-labeling-handoff","https://datacenterlabeling.com/problems/label-audit-evidence"],"markdownUrl":"https://datacenterlabeling.com/guides/choosing-a-label-printer.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/guides/choosing-a-label-printer#quick-answer"},{"id":"start-with-a-print-job-not-a-product-category","title":"Start with a print job, not a product category","canonicalUrl":"https://datacenterlabeling.com/guides/choosing-a-label-printer#start-with-a-print-job-not-a-product-category"},{"id":"define-the-workload-and-the-unit-you-are-counting","title":"Define the workload and the unit you are counting","canonicalUrl":"https://datacenterlabeling.com/guides/choosing-a-label-printer#define-the-workload-and-the-unit-you-are-counting"},{"id":"portable-desktop-or-a-shared-workflow","title":"Portable, desktop, or a shared workflow?","canonicalUrl":"https://datacenterlabeling.com/guides/choosing-a-label-printer#portable-desktop-or-a-shared-workflow"},{"id":"qualify-the-complete-printing-and-material-combination","title":"Qualify the complete printing and material combination","canonicalUrl":"https://datacenterlabeling.com/guides/choosing-a-label-printer#qualify-the-complete-printing-and-material-combination"},{"id":"make-the-software-prove-its-place-in-the-workflow","title":"Make the software prove its place in the workflow","canonicalUrl":"https://datacenterlabeling.com/guides/choosing-a-label-printer#make-the-software-prove-its-place-in-the-workflow"},{"id":"check-connectivity-access-and-support-before-purchase","title":"Check connectivity, access, and support before purchase","canonicalUrl":"https://datacenterlabeling.com/guides/choosing-a-label-printer#check-connectivity-access-and-support-before-purchase"},{"id":"run-a-controlled-representative-trial","title":"Run a controlled, representative trial","canonicalUrl":"https://datacenterlabeling.com/guides/choosing-a-label-printer#run-a-controlled-representative-trial"},{"id":"worked-example-count-accepted-labels-then-calculate-cost","title":"Worked example: count accepted labels, then calculate cost","canonicalUrl":"https://datacenterlabeling.com/guides/choosing-a-label-printer#worked-example-count-accepted-labels-then-calculate-cost"},{"id":"avoid-misleading-total-cost-comparisons","title":"Avoid misleading total-cost comparisons","canonicalUrl":"https://datacenterlabeling.com/guides/choosing-a-label-printer#avoid-misleading-total-cost-comparisons"},{"id":"when-a-printer-is-already-installed","title":"When a printer is already installed","canonicalUrl":"https://datacenterlabeling.com/guides/choosing-a-label-printer#when-a-printer-is-already-installed"},{"id":"acceptance-checklist","title":"Acceptance checklist","canonicalUrl":"https://datacenterlabeling.com/guides/choosing-a-label-printer#acceptance-checklist"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/guides/choosing-a-label-printer#frequently-asked-questions"},{"id":"use-the-planning-template","title":"Use the planning template","canonicalUrl":"https://datacenterlabeling.com/guides/choosing-a-label-printer#use-the-planning-template"}]},{"slug":"rfid-aim-or-barcodes","title":"Choose barcodes, RFID, or AIM for the evidence you need","dek":"Separate asset inventory from connection detection, test the actual environment, and decide who turns observations into trusted records.","summary":"Choose the technology by the observation you need: deliberate barcode lookup, qualified RFID inventory, or supported AIM connection events. Keep asset identity, location, and connectivity as separate claims. Test an independently known population, missed observations, outside-area reads, and record integration before accepting the workflow. A tag read alone does not establish a rack location or a complete cable path.","category":"Planning & decisions","canonicalUrl":"https://datacenterlabeling.com/guides/rfid-aim-or-barcodes","route":"/guides/rfid-aim-or-barcodes","sourceIds":["S43","S44","S45","S46"],"templateIds":["identification-technology-pilot-plan"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/asset-versus-location","https://datacenterlabeling.com/problems/cable-endpoint-identification","https://datacenterlabeling.com/problems/patch-panel-port-mapping","https://datacenterlabeling.com/problems/barcode-qr-scan-quality","https://datacenterlabeling.com/problems/label-record-reconciliation","https://datacenterlabeling.com/problems/contractor-labeling-handoff","https://datacenterlabeling.com/problems/moves-and-retirement-closeout","https://datacenterlabeling.com/problems/label-audit-evidence"],"markdownUrl":"https://datacenterlabeling.com/guides/rfid-aim-or-barcodes.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/guides/rfid-aim-or-barcodes#quick-answer"},{"id":"decide-what-observation-would-answer-the-question","title":"Decide what observation would answer the question","canonicalUrl":"https://datacenterlabeling.com/guides/rfid-aim-or-barcodes#decide-what-observation-would-answer-the-question"},{"id":"compare-the-job-not-just-the-technology","title":"Compare the job, not just the technology","canonicalUrl":"https://datacenterlabeling.com/guides/rfid-aim-or-barcodes#compare-the-job-not-just-the-technology"},{"id":"keep-identity-location-and-connection-separate","title":"Keep identity, location, and connection separate","canonicalUrl":"https://datacenterlabeling.com/guides/rfid-aim-or-barcodes#keep-identity-location-and-connection-separate"},{"id":"qualify-the-physical-environment-and-read-boundary","title":"Qualify the physical environment and read boundary","canonicalUrl":"https://datacenterlabeling.com/guides/rfid-aim-or-barcodes#qualify-the-physical-environment-and-read-boundary"},{"id":"design-a-pilot-that-can-fail-honestly","title":"Design a pilot that can fail honestly","canonicalUrl":"https://datacenterlabeling.com/guides/rfid-aim-or-barcodes#design-a-pilot-that-can-fail-honestly"},{"id":"worked-fictional-case-a-better-count-still-fails-the-boundary","title":"Worked fictional case: a better count still fails the boundary","canonicalUrl":"https://datacenterlabeling.com/guides/rfid-aim-or-barcodes#worked-fictional-case-a-better-count-still-fails-the-boundary"},{"id":"assign-ownership-and-compare-the-complete-effort","title":"Assign ownership and compare the complete effort","canonicalUrl":"https://datacenterlabeling.com/guides/rfid-aim-or-barcodes#assign-ownership-and-compare-the-complete-effort"},{"id":"acceptance-checklist","title":"Acceptance checklist","canonicalUrl":"https://datacenterlabeling.com/guides/rfid-aim-or-barcodes#acceptance-checklist"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/guides/rfid-aim-or-barcodes#frequently-asked-questions"},{"id":"use-the-planning-template","title":"Use the planning template","canonicalUrl":"https://datacenterlabeling.com/guides/rfid-aim-or-barcodes#use-the-planning-template"}]},{"slug":"cable-color-legends","title":"Create a cable-color legend people can use","dek":"Define what each cue means, preserve readable identity, and migrate conflicting local schemes without making jacket color the only answer.","summary":"Define a cable-color legend by its meaning, physical carrier, location scope, and owner. Keep the unique cable ID and readable service text available when color is unclear. Reconcile conflicting legends before releasing a transition, and track field markers, records, and templates through the change. Treat local palette choices separately from equipment markings and any verified external requirements.","category":"Planning & decisions","canonicalUrl":"https://datacenterlabeling.com/guides/cable-color-legends","route":"/guides/cable-color-legends","sourceIds":["S01","S47"],"templateIds":["cable-color-legends-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/naming-convention","https://datacenterlabeling.com/problems/cable-endpoint-identification","https://datacenterlabeling.com/problems/fiber-trunk-breakout-map","https://datacenterlabeling.com/problems/a-b-power-feed-identification","https://datacenterlabeling.com/problems/operational-versus-safety-labels","https://datacenterlabeling.com/problems/label-fit-and-readability"],"markdownUrl":"https://datacenterlabeling.com/guides/cable-color-legends.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/guides/cable-color-legends#quick-answer"},{"id":"start-with-the-identification-task","title":"Start with the identification task","canonicalUrl":"https://datacenterlabeling.com/guides/cable-color-legends#start-with-the-identification-task"},{"id":"inventory-meanings-before-choosing-a-palette","title":"Inventory meanings before choosing a palette","canonicalUrl":"https://datacenterlabeling.com/guides/cable-color-legends#inventory-meanings-before-choosing-a-palette"},{"id":"choose-the-correction-branch","title":"Choose the correction branch","canonicalUrl":"https://datacenterlabeling.com/guides/cable-color-legends#choose-the-correction-branch"},{"id":"make-the-information-available-without-hue","title":"Make the information available without hue","canonicalUrl":"https://datacenterlabeling.com/guides/cable-color-legends#make-the-information-available-without-hue"},{"id":"worked-case-blue-means-two-things","title":"Worked case: blue means two things","canonicalUrl":"https://datacenterlabeling.com/guides/cable-color-legends#worked-case-blue-means-two-things"},{"id":"release-the-transition-as-a-set-of-current-states","title":"Release the transition as a set of current states","canonicalUrl":"https://datacenterlabeling.com/guides/cable-color-legends#release-the-transition-as-a-set-of-current-states"},{"id":"acceptance-checklist","title":"Acceptance checklist","canonicalUrl":"https://datacenterlabeling.com/guides/cable-color-legends#acceptance-checklist"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/guides/cable-color-legends#frequently-asked-questions"}]},{"slug":"legacy-room-relabeling","title":"Plan a legacy-room relabeling program","dek":"Build a credible baseline, resolve unknowns through their owners, and release manageable waves with physical and record evidence.","summary":"Plan legacy-room relabeling around a bounded population, an evidence-based baseline, and named owners for unknown identities. Sequence small work packages by their information dependencies, then use a representative pilot to estimate routine and exception effort. Release definitive labels from accepted records and close physical and record checks together. Partial acceptance must identify the completed objects and the obligations still open.","category":"Planning & decisions","canonicalUrl":"https://datacenterlabeling.com/guides/legacy-room-relabeling","route":"/guides/legacy-room-relabeling","sourceIds":["S40","S01"],"templateIds":["legacy-room-relabeling-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/naming-convention","https://datacenterlabeling.com/problems/duplicate-identifiers","https://datacenterlabeling.com/problems/rack-wayfinding","https://datacenterlabeling.com/problems/rack-face-and-u-position","https://datacenterlabeling.com/problems/cable-endpoint-identification","https://datacenterlabeling.com/problems/patch-panel-port-mapping","https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking","https://datacenterlabeling.com/problems/label-material-failure","https://datacenterlabeling.com/problems/bulk-label-import","https://datacenterlabeling.com/problems/label-record-reconciliation","https://datacenterlabeling.com/problems/contractor-labeling-handoff","https://datacenterlabeling.com/problems/moves-and-retirement-closeout","https://datacenterlabeling.com/problems/label-audit-evidence"],"markdownUrl":"https://datacenterlabeling.com/guides/legacy-room-relabeling.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/guides/legacy-room-relabeling#quick-answer"},{"id":"begin-with-a-bounded-recovery-project","title":"Begin with a bounded recovery project","canonicalUrl":"https://datacenterlabeling.com/guides/legacy-room-relabeling#begin-with-a-bounded-recovery-project"},{"id":"build-a-baseline-that-does-not-claim-more-than-it-knows","title":"Build a baseline that does not claim more than it knows","canonicalUrl":"https://datacenterlabeling.com/guides/legacy-room-relabeling#build-a-baseline-that-does-not-claim-more-than-it-knows"},{"id":"assign-owners-and-information-dependencies","title":"Assign owners and information dependencies","canonicalUrl":"https://datacenterlabeling.com/guides/legacy-room-relabeling#assign-owners-and-information-dependencies"},{"id":"choose-the-next-work-package","title":"Choose the next work package","canonicalUrl":"https://datacenterlabeling.com/guides/legacy-room-relabeling#choose-the-next-work-package"},{"id":"pilot-representative-conditions-and-measure-the-work","title":"Pilot representative conditions and measure the work","canonicalUrl":"https://datacenterlabeling.com/guides/legacy-room-relabeling#pilot-representative-conditions-and-measure-the-work"},{"id":"worked-case-a-two-rack-pilot-leaves-an-honest-exception-queue","title":"Worked case: a two-rack pilot leaves an honest exception queue","canonicalUrl":"https://datacenterlabeling.com/guides/legacy-room-relabeling#worked-case-a-two-rack-pilot-leaves-an-honest-exception-queue"},{"id":"release-waves-through-physical-and-record-gates","title":"Release waves through physical and record gates","canonicalUrl":"https://datacenterlabeling.com/guides/legacy-room-relabeling#release-waves-through-physical-and-record-gates"},{"id":"acceptance-checklist","title":"Acceptance checklist","canonicalUrl":"https://datacenterlabeling.com/guides/legacy-room-relabeling#acceptance-checklist"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/guides/legacy-room-relabeling#frequently-asked-questions"}]},{"slug":"labeling-business-case","title":"Build a labeling budget and business case","dek":"Compare the actual cost of implementation and upkeep with conservative, evidence-based improvements in lookup and rework effort.","summary":"Build a labeling business case from a defined workload, comparable baseline and pilot tasks, and explicit one-time and recurring costs. Use conservative scenarios for eligible events and supported time improvements. Separate labor-valued capacity from actual cash savings, and account for waste and ongoing upkeep. Keep unverified benefits visible as assumptions and check actual outcomes after the accepted scope is implemented.","category":"Planning & decisions","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-business-case","route":"/guides/labeling-business-case","sourceIds":["S01","S26"],"templateIds":["labeling-business-case-planning-template"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/label-material-failure","https://datacenterlabeling.com/problems/label-fit-and-readability","https://datacenterlabeling.com/problems/label-print-quality","https://datacenterlabeling.com/problems/bulk-label-import","https://datacenterlabeling.com/problems/label-record-reconciliation","https://datacenterlabeling.com/problems/moves-and-retirement-closeout","https://datacenterlabeling.com/problems/label-audit-evidence"],"markdownUrl":"https://datacenterlabeling.com/guides/labeling-business-case.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-business-case#quick-answer"},{"id":"define-the-decision-before-collecting-impressive-numbers","title":"Define the decision before collecting impressive numbers","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-business-case#define-the-decision-before-collecting-impressive-numbers"},{"id":"measure-a-comparable-baseline","title":"Measure a comparable baseline","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-business-case#measure-a-comparable-baseline"},{"id":"count-the-complete-implementation-and-upkeep-cost","title":"Count the complete implementation and upkeep cost","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-business-case#count-the-complete-implementation-and-upkeep-cost"},{"id":"choose-a-conservative-benefit-scenario","title":"Choose a conservative benefit scenario","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-business-case#choose-a-conservative-benefit-scenario"},{"id":"worked-fictional-case-the-base-scenario-is-less-attractive-than-the-pilot","title":"Worked fictional case: the base scenario is less attractive than the pilot","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-business-case#worked-fictional-case-the-base-scenario-is-less-attractive-than-the-pilot"},{"id":"decide-what-the-evidence-supports","title":"Decide what the evidence supports","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-business-case#decide-what-the-evidence-supports"},{"id":"keep-risk-arguments-separate-from-the-arithmetic","title":"Keep risk arguments separate from the arithmetic","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-business-case#keep-risk-arguments-separate-from-the-arithmetic"},{"id":"acceptance-checklist","title":"Acceptance checklist","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-business-case#acceptance-checklist"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-business-case#frequently-asked-questions"}]},{"slug":"labeling-standards-and-project-requirements","title":"Data center labeling standards: build a project requirements map","dek":"Separate identifier administration, equipment instructions, safety markings, and material claims before turning a standard name into a labeling rule.","summary":"Map labeling requirements by function: identifier administration, equipment placement, safety messages, materials, records, and acceptance. Record each governing document, edition, applicability decision, and evidence actually reviewed. Public scope pages help locate the relevant source; precise requirements need the applicable authorized text. Keep local naming choices explicit, qualify material claims to their stated conditions, and route technical conflicts to the responsible owner.","category":"Planning & decisions","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-standards-and-project-requirements","route":"/guides/labeling-standards-and-project-requirements","sourceIds":["S01","S31","S48","S30"],"templateIds":["site-labeling-standard","labeling-handoff-specification"],"sourceReviewDate":"2026-09-12","relatedUrls":["https://datacenterlabeling.com/problems/naming-convention","https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking","https://datacenterlabeling.com/problems/operational-versus-safety-labels","https://datacenterlabeling.com/problems/cooling-pipe-identification","https://datacenterlabeling.com/problems/label-material-failure","https://datacenterlabeling.com/problems/contractor-labeling-handoff","https://datacenterlabeling.com/problems/label-audit-evidence"],"markdownUrl":"https://datacenterlabeling.com/guides/labeling-standards-and-project-requirements.md","sections":[{"id":"quick-answer","title":"The practical answer","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-standards-and-project-requirements#quick-answer"},{"id":"start-with-the-decision-the-label-supports","title":"Start with the decision the label supports","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-standards-and-project-requirements#start-with-the-decision-the-label-supports"},{"id":"put-each-source-in-the-right-role","title":"Put each source in the right role","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-standards-and-project-requirements#put-each-source-in-the-right-role"},{"id":"record-edition-applicability-and-access-separately","title":"Record edition, applicability, and access separately","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-standards-and-project-requirements#record-edition-applicability-and-access-separately"},{"id":"translate-a-requirement-into-observable-acceptance","title":"Translate a requirement into observable acceptance","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-standards-and-project-requirements#translate-a-requirement-into-observable-acceptance"},{"id":"interpret-material-recognition-without-expanding-its-scope","title":"Interpret material recognition without expanding its scope","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-standards-and-project-requirements#interpret-material-recognition-without-expanding-its-scope"},{"id":"worked-case-one-specification-contains-three-different-questions","title":"Worked case: one specification contains three different questions","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-standards-and-project-requirements#worked-case-one-specification-contains-three-different-questions"},{"id":"manage-disagreements-without-erasing-evidence","title":"Manage disagreements without erasing evidence","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-standards-and-project-requirements#manage-disagreements-without-erasing-evidence"},{"id":"acceptance-checklist","title":"Acceptance checklist","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-standards-and-project-requirements#acceptance-checklist"},{"id":"frequently-asked-questions","title":"Frequently asked questions","canonicalUrl":"https://datacenterlabeling.com/guides/labeling-standards-and-project-requirements#frequently-asked-questions"}]}],"templates":[{"id":"worksheet-1","title":"Naming convention worksheet","description":"Define object types, uniqueness scope, field meanings, allowed values, and an issuance owner in the editable naming-convention worksheet.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/naming-convention","markdownUrl":"https://datacenterlabeling.com/templates/naming-convention.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"01 Naming policy","guideSlugs":["naming-convention"]},{"id":"worksheet-2","title":"Identifier collision register","description":"Classify duplicate IDs, compare competing records, and document replacement decisions, owners, and verification in the identifier collision register.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/duplicate-identifiers","markdownUrl":"https://datacenterlabeling.com/templates/duplicate-identifiers.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"02 Duplicate IDs","guideSlugs":["duplicate-identifiers"]},{"id":"worksheet-3","title":"Rack and row sign schedule","description":"Survey rack and row signs by site, room, map reference, approach, and sign position. Record route observations and verification in the editable schedule.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/rack-wayfinding","markdownUrl":"https://datacenterlabeling.com/templates/rack-wayfinding.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"03 Rack wayfinding","guideSlugs":["rack-wayfinding"]},{"id":"worksheet-4","title":"Rack elevation and label-placement worksheet","description":"Record mounting face, occupied rack units, equipment height, and position rules in the editable rack-elevation and label-placement worksheet.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/rack-face-and-u-position","markdownUrl":"https://datacenterlabeling.com/templates/rack-face-and-u-position.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"04 Rack face and U","guideSlugs":["rack-face-and-u-position"]},{"id":"worksheet-5","title":"Asset-to-location crosswalk","description":"Maintain asset IDs, serial numbers, hostnames, previous and current locations, and change references in the editable asset-to-location crosswalk.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/asset-versus-location","markdownUrl":"https://datacenterlabeling.com/templates/asset-versus-location.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"05 Asset and location","guideSlugs":["asset-versus-location"]},{"id":"worksheet-6","title":"Two-end cable label schedule","description":"Prepare paired cable labels with local and remote endpoints, connection references, exceptions, and verification evidence in an editable Excel schedule.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/cable-endpoint-identification","markdownUrl":"https://datacenterlabeling.com/templates/cable-endpoint-identification.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"06 Cable endpoints","guideSlugs":["cable-endpoint-identification"]},{"id":"worksheet-7","title":"Patch-panel map and strip proof sheet","description":"Record panel models, factory ports, grouping, spacing, and printed-proof results in the editable patch-panel mapping and strip-proof worksheet.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/patch-panel-port-mapping","markdownUrl":"https://datacenterlabeling.com/templates/patch-panel-port-mapping.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"07 Panel port mapping","guideSlugs":["patch-panel-port-mapping"]},{"id":"worksheet-8","title":"Fiber trunk and breakout mapping sheet","description":"Map trunk IDs, assembly revisions, local hierarchies, legs or fibers, remote endpoints, and separate polarity evidence in the editable fiber worksheet.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/fiber-trunk-breakout-map","markdownUrl":"https://datacenterlabeling.com/templates/fiber-trunk-breakout-map.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"08 Fiber breakout","guideSlugs":["fiber-trunk-breakout-map"]},{"id":"worksheet-9","title":"Dense-rack placement checklist","description":"Compare cable diameter, marker part, service viewpoint, placement, and installed reading results in the dense-rack label checklist.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/dense-rack-label-visibility","markdownUrl":"https://datacenterlabeling.com/templates/dense-rack-label-visibility.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"09 Dense rack labels","guideSlugs":["dense-rack-label-visibility"]},{"id":"worksheet-10","title":"GPU cable staging manifest","description":"Track bundle sequence, cable IDs, endpoints, type, length, kit checks, and manifest revision in the editable GPU cable staging worksheet.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/gpu-cable-staging","markdownUrl":"https://datacenterlabeling.com/templates/gpu-cable-staging.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"10 GPU cable staging","guideSlugs":["gpu-cable-staging"]},{"id":"worksheet-11","title":"A/B feed identification worksheet","description":"Compare observed PDU text, A/B designation, upstream source, and the approved legend in the editable feed-identification worksheet.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/a-b-power-feed-identification","markdownUrl":"https://datacenterlabeling.com/templates/a-b-power-feed-identification.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"11 A-B feeds","guideSlugs":["a-b-power-feed-identification"]},{"id":"worksheet-12","title":"Circuit and disconnect marking survey","description":"Document equipment, location, observed purpose, reference documents, findings, and owner decisions in the circuit and disconnect marking survey.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/panel-circuit-disconnect-marking","markdownUrl":"https://datacenterlabeling.com/templates/panel-circuit-disconnect-marking.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"12 Circuit markings","guideSlugs":["panel-circuit-disconnect-marking"]},{"id":"worksheet-13","title":"PDU outlet-to-PSU connection schedule","description":"Match each cord to its rack, PDU outlet, device asset, PSU or inlet, and record reference in the editable connection schedule.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/pdu-outlet-psu-map","markdownUrl":"https://datacenterlabeling.com/templates/pdu-outlet-psu-map.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"13 PDU to PSU","guideSlugs":["pdu-outlet-psu-map"]},{"id":"worksheet-14","title":"Bonding identification register","description":"Record conductor IDs, equipment and busbar endpoints, drawing references, findings, and evidence in the editable bonding register.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/grounding-bonding-identification","markdownUrl":"https://datacenterlabeling.com/templates/grounding-bonding-identification.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"14 Bonding IDs","guideSlugs":["grounding-bonding-identification"]},{"id":"worksheet-15","title":"Safety-label visibility and reference checklist","description":"Classify label functions, inspect visibility and condition, and record approved references and dispositions in the safety-label review worksheet.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/operational-versus-safety-labels","markdownUrl":"https://datacenterlabeling.com/templates/operational-versus-safety-labels.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"15 Safety label review","guideSlugs":["operational-versus-safety-labels"]},{"id":"worksheet-16","title":"Cooling pipe-marker survey","description":"Survey loop IDs, fluid descriptions, documented service roles, flow directions, and observed markers in the editable cooling-pipe worksheet.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/cooling-pipe-identification","markdownUrl":"https://datacenterlabeling.com/templates/cooling-pipe-identification.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"16 Pipe markers","guideSlugs":["cooling-pipe-identification"]},{"id":"worksheet-17","title":"Liquid-cooling hose connection register","description":"Record hose IDs, equipment models, factory markings, manifold and remote endpoints, roles, and OEM diagrams in the hose connection register.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/liquid-cooling-hose-endpoints","markdownUrl":"https://datacenterlabeling.com/templates/liquid-cooling-hose-endpoints.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"17 Cooling hoses","guideSlugs":["liquid-cooling-hose-endpoints"]},{"id":"worksheet-18","title":"Facility equipment and alarm-name crosswalk","description":"Link BMS alarm names and point references to physical equipment, location, model, drawings, and evidence in the editable crosswalk.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/facility-equipment-name-crosswalk","markdownUrl":"https://datacenterlabeling.com/templates/facility-equipment-name-crosswalk.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"18 Equipment aliases","guideSlugs":["facility-equipment-name-crosswalk"]},{"id":"worksheet-19","title":"Pathway and penetration identification schedule","description":"Map pathway and penetration IDs to bounded segments, adjacent routes, drawing grids, and linked cables in the editable identification schedule.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/pathway-route-identification","markdownUrl":"https://datacenterlabeling.com/templates/pathway-route-identification.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"19 Pathway IDs","guideSlugs":["pathway-route-identification"]},{"id":"worksheet-20","title":"Colocation demarcation and ID crosswalk","description":"Preserve provider, cross-connect, and tenant IDs with A/Z demarcations, LOA references, and onward patching in the editable crosswalk.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/colocation-demarcation","markdownUrl":"https://datacenterlabeling.com/templates/colocation-demarcation.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"20 Colo demarcation","guideSlugs":["colocation-demarcation"]},{"id":"worksheet-21","title":"Label material qualification worksheet","description":"Qualify label and ribbon combinations against the surface, application conditions, service exposure, and observed sample results in the editable worksheet.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/label-material-failure","markdownUrl":"https://datacenterlabeling.com/templates/label-material-failure.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"21 Label materials","guideSlugs":["label-material-failure"]},{"id":"worksheet-22","title":"Label fit and readability worksheet","description":"Compare measured geometry, usable print area, exact legends, termination state, and clearance checks in the editable label-fit worksheet.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/label-fit-and-readability","markdownUrl":"https://datacenterlabeling.com/templates/label-fit-and-readability.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"22 Label fit","guideSlugs":["label-fit-and-readability"]},{"id":"worksheet-23","title":"Printer setup and proof record","description":"Retain printer, template, media, ribbon, settings, and printed-proof evidence in the editable setup and print-quality record.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/label-print-quality","markdownUrl":"https://datacenterlabeling.com/templates/label-print-quality.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"23 Print quality","guideSlugs":["label-print-quality"]},{"id":"worksheet-24","title":"Bulk-label data preparation and batch checklist","description":"Compare source and preview IDs, endpoint fields, original copies, reprints, and release decisions in the editable bulk-label batch checklist.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/bulk-label-import","markdownUrl":"https://datacenterlabeling.com/templates/bulk-label-import.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"24 Bulk label import","guideSlugs":["bulk-label-import"]},{"id":"worksheet-25","title":"Barcode and QR acceptance test sheet","description":"Compare expected and decoded payloads, symbol size, scanner profiles, scan outcomes, and record lookups in the barcode and QR acceptance sheet.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/barcode-qr-scan-quality","markdownUrl":"https://datacenterlabeling.com/templates/barcode-qr-scan-quality.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"25 Barcode checks","guideSlugs":["barcode-qr-scan-quality"]},{"id":"worksheet-26","title":"Label-to-record reconciliation register","description":"Compare observed and system values by disputed field, record owner, approved decision, and evidence in the editable reconciliation register.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/label-record-reconciliation","markdownUrl":"https://datacenterlabeling.com/templates/label-record-reconciliation.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"26 Record reconciliation","guideSlugs":["label-record-reconciliation"]},{"id":"worksheet-27","title":"Cable-label and test-result reconciliation sheet","description":"Cross-reference planned, applied, and original test IDs with endpoints, result references, identity status, and technical review in the editable sheet.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/cable-test-id-reconciliation","markdownUrl":"https://datacenterlabeling.com/templates/cable-test-id-reconciliation.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"27 Test ID matching","guideSlugs":["cable-test-id-reconciliation"]},{"id":"worksheet-28","title":"Contractor labeling handover checklist","description":"Review delivered scope, policy revisions, label schedules, as-builts, test indexes, and punch-list states in the contractor handover checklist.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/contractor-labeling-handoff","markdownUrl":"https://datacenterlabeling.com/templates/contractor-labeling-handoff.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"28 Contractor handoff","guideSlugs":["contractor-labeling-handoff"]},{"id":"worksheet-29","title":"Moves, additions, changes, and retirement closeout sheet","description":"Account for old and final states, object IDs, migration waves, physical labels, evidence, and closure in the editable change and retirement sheet.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/moves-and-retirement-closeout","markdownUrl":"https://datacenterlabeling.com/templates/moves-and-retirement-closeout.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"29 Change closeout","guideSlugs":["moves-and-retirement-closeout"]},{"id":"worksheet-30","title":"Label audit and exception register","description":"Define the audit scope and criteria, log observed findings, and retain corrections, evidence, reviewers, and closure in the label-audit register.","format":"xlsx","canonicalUrl":"https://datacenterlabeling.com/templates/label-audit-evidence","markdownUrl":"https://datacenterlabeling.com/templates/label-audit-evidence.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx","workbookTab":"30 Audit evidence","guideSlugs":["label-audit-evidence"]},{"id":"site-labeling-standard","title":"Site labeling standard template","description":"Define scope, identifiers, records, material acceptance, and change ownership in one editable policy.","format":"markdown","canonicalUrl":"https://datacenterlabeling.com/planning-templates/site-labeling-standard","markdownUrl":"https://datacenterlabeling.com/planning-templates/site-labeling-standard.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/planning/site-labeling-standard.md","guideSlugs":["labeling-standards-and-project-requirements","naming-convention","duplicate-identifiers","label-material-failure","contractor-labeling-handoff","moves-and-retirement-closeout"]},{"id":"multi-site-prefix-register","title":"Multi-site prefix and alias register","description":"Reserve site prefixes, document ownership, and preserve mappings when sites merge or change names.","format":"markdown","canonicalUrl":"https://datacenterlabeling.com/planning-templates/multi-site-prefix-register","markdownUrl":"https://datacenterlabeling.com/planning-templates/multi-site-prefix-register.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/planning/multi-site-prefix-register.md","guideSlugs":["naming-convention","duplicate-identifiers","rack-wayfinding","asset-versus-location"]},{"id":"patch-panel-print-proof","title":"Patch-panel layout and print-proof record","description":"Measure port geometry, preserve numbering, and accept a physical print before producing a full batch.","format":"markdown","canonicalUrl":"https://datacenterlabeling.com/planning-templates/patch-panel-print-proof","markdownUrl":"https://datacenterlabeling.com/planning-templates/patch-panel-print-proof.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/planning/patch-panel-print-proof.md","guideSlugs":["patch-panel-port-mapping","label-fit-and-readability","label-print-quality","bulk-label-import"]},{"id":"labeling-handoff-specification","title":"Labeling scope and handoff specification","description":"Set reviewable requirements for naming, material proofs, records, exceptions, and acceptance before installation.","format":"markdown","canonicalUrl":"https://datacenterlabeling.com/planning-templates/labeling-handoff-specification","markdownUrl":"https://datacenterlabeling.com/planning-templates/labeling-handoff-specification.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/planning/labeling-handoff-specification.md","guideSlugs":["labeling-standards-and-project-requirements","naming-convention","colocation-demarcation","label-material-failure","cable-test-id-reconciliation","contractor-labeling-handoff","label-audit-evidence"]},{"id":"change-ticket-labeling-closeout","title":"Move, add, change, and retirement ticket insert","description":"Carry old and new identifiers, label actions, record corrections, and evidence into the change ticket.","format":"markdown","canonicalUrl":"https://datacenterlabeling.com/planning-templates/change-ticket-labeling-closeout","markdownUrl":"https://datacenterlabeling.com/planning-templates/change-ticket-labeling-closeout.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/planning/change-ticket-labeling-closeout.md","guideSlugs":["asset-versus-location","cable-endpoint-identification","label-record-reconciliation","moves-and-retirement-closeout"]},{"id":"remote-hands-cabinet-brief","title":"Remote-hands cabinet identification brief","description":"Give a remote technician a scoped cabinet identity, relevant records, expected observations, and escalation route.","format":"markdown","canonicalUrl":"https://datacenterlabeling.com/planning-templates/remote-hands-cabinet-brief","markdownUrl":"https://datacenterlabeling.com/planning-templates/remote-hands-cabinet-brief.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/planning/remote-hands-cabinet-brief.md","guideSlugs":["rack-wayfinding","asset-versus-location","cable-endpoint-identification","a-b-power-feed-identification","pdu-outlet-psu-map","colocation-demarcation","label-record-reconciliation","contractor-labeling-handoff"]},{"id":"fiber-assembly-reference-record","title":"Fiber assembly and mapping reference record","description":"Collect actual assembly, cassette, and polarity references while preserving unknowns and separate acceptance evidence.","format":"markdown","canonicalUrl":"https://datacenterlabeling.com/planning-templates/fiber-assembly-reference-record","markdownUrl":"https://datacenterlabeling.com/planning-templates/fiber-assembly-reference-record.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/planning/fiber-assembly-reference-record.md","guideSlugs":["fiber-trunk-breakout-map","dense-rack-label-visibility","label-fit-and-readability","cable-test-id-reconciliation"]},{"id":"panel-port-relationship-schedule","title":"Panel and switch port relationship schedule","description":"Join physical ports, connected interfaces, cable identities, and record revisions without losing blank or reserved positions.","format":"markdown","canonicalUrl":"https://datacenterlabeling.com/planning-templates/panel-port-relationship-schedule","markdownUrl":"https://datacenterlabeling.com/planning-templates/panel-port-relationship-schedule.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/planning/panel-port-relationship-schedule.md","guideSlugs":["cable-endpoint-identification","patch-panel-port-mapping","fiber-trunk-breakout-map","bulk-label-import","label-record-reconciliation"]},{"id":"device-label-placement-review","title":"Device-class label placement review","description":"Compare approved surfaces and real reading tasks across servers, switches, rack PDUs, and facility equipment.","format":"markdown","canonicalUrl":"https://datacenterlabeling.com/planning-templates/device-label-placement-review","markdownUrl":"https://datacenterlabeling.com/planning-templates/device-label-placement-review.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/planning/device-label-placement-review.md","guideSlugs":["rack-face-and-u-position","asset-versus-location","dense-rack-label-visibility","operational-versus-safety-labels","label-fit-and-readability","barcode-qr-scan-quality"]},{"id":"cooling-and-facility-signage-crosswalk","title":"Cooling and facility signage crosswalk","description":"Keep hose endpoints, cooling systems, alarms, leak zones, and owned signs connected without treating them as interchangeable IDs.","format":"markdown","canonicalUrl":"https://datacenterlabeling.com/planning-templates/cooling-and-facility-signage-crosswalk","markdownUrl":"https://datacenterlabeling.com/planning-templates/cooling-and-facility-signage-crosswalk.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/planning/cooling-and-facility-signage-crosswalk.md","guideSlugs":["operational-versus-safety-labels","cooling-pipe-identification","liquid-cooling-hose-endpoints","facility-equipment-name-crosswalk","pathway-route-identification"]},{"id":"label-printer-selection-plan","title":"Label printer selection and trial plan","description":"Use this editable planning record with choose a label printer for the work you actually do.","format":"markdown","canonicalUrl":"https://datacenterlabeling.com/planning-templates/label-printer-selection-plan","markdownUrl":"https://datacenterlabeling.com/planning-templates/label-printer-selection-plan.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/planning/label-printer-selection-plan.md","guideSlugs":["choosing-a-label-printer","cable-endpoint-identification","patch-panel-port-mapping","label-material-failure","label-fit-and-readability","label-print-quality","bulk-label-import","barcode-qr-scan-quality","contractor-labeling-handoff","label-audit-evidence"]},{"id":"identification-technology-pilot-plan","title":"Barcode, RFID and AIM technology pilot plan","description":"Use this editable planning record with choose barcodes, rfid, or aim for the evidence you need.","format":"markdown","canonicalUrl":"https://datacenterlabeling.com/planning-templates/identification-technology-pilot-plan","markdownUrl":"https://datacenterlabeling.com/planning-templates/identification-technology-pilot-plan.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/planning/identification-technology-pilot-plan.md","guideSlugs":["rfid-aim-or-barcodes","asset-versus-location","cable-endpoint-identification","patch-panel-port-mapping","barcode-qr-scan-quality","label-record-reconciliation","contractor-labeling-handoff","moves-and-retirement-closeout","label-audit-evidence"]},{"id":"cable-color-legends-planning-template","title":"Cable-color meaning and transition planning register","description":"Use this editable planning record with create a cable-color legend people can use.","format":"markdown","canonicalUrl":"https://datacenterlabeling.com/planning-templates/cable-color-legends-planning-template","markdownUrl":"https://datacenterlabeling.com/planning-templates/cable-color-legends-planning-template.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/planning/cable-color-legends-planning-template.md","guideSlugs":["cable-color-legends","naming-convention","cable-endpoint-identification","fiber-trunk-breakout-map","a-b-power-feed-identification","operational-versus-safety-labels","label-fit-and-readability"]},{"id":"legacy-room-relabeling-planning-template","title":"Legacy-room baseline, wave, and uncertainty planning template","description":"Use this editable planning record with plan a legacy-room relabeling program.","format":"markdown","canonicalUrl":"https://datacenterlabeling.com/planning-templates/legacy-room-relabeling-planning-template","markdownUrl":"https://datacenterlabeling.com/planning-templates/legacy-room-relabeling-planning-template.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/planning/legacy-room-relabeling-planning-template.md","guideSlugs":["legacy-room-relabeling","naming-convention","duplicate-identifiers","rack-wayfinding","rack-face-and-u-position","cable-endpoint-identification","patch-panel-port-mapping","panel-circuit-disconnect-marking","label-material-failure","bulk-label-import","label-record-reconciliation","contractor-labeling-handoff","moves-and-retirement-closeout","label-audit-evidence"]},{"id":"labeling-business-case-planning-template","title":"Measured labeling cost and benefit planning template","description":"Use this editable planning record with build a labeling budget and business case.","format":"markdown","canonicalUrl":"https://datacenterlabeling.com/planning-templates/labeling-business-case-planning-template","markdownUrl":"https://datacenterlabeling.com/planning-templates/labeling-business-case-planning-template.md","downloadUrl":"https://datacenterlabeling.com/assets/downloads/planning/labeling-business-case-planning-template.md","guideSlugs":["labeling-business-case","label-material-failure","label-fit-and-readability","label-print-quality","bulk-label-import","label-record-reconciliation","moves-and-retirement-closeout","label-audit-evidence"]}],"sources":[{"id":"S01","title":"TIA FOTC: TIA-606-D scope","url":"https://www.tiafotc.org/tia-standards-update/tia-606-d/","note":"Public scope overview; local patterns and review workflow are editorial examples, not normative syntax.","scope":"The TIA FOTC overview establishes the administration scope and identifies records, relationships, reports, and administration classes. It is a scope overview rather than a full clause-by-clause review.","canonicalUrl":"https://datacenterlabeling.com/references/s01","markdownUrl":"https://datacenterlabeling.com/references/s01.md","guideSlugs":["naming-convention","pathway-route-identification","cable-color-legends","legacy-room-relabeling","labeling-business-case","labeling-standards-and-project-requirements"],"reviewedAt":"2026-09-12"},{"id":"S02","title":"ServiceNow: Identification and reconciliation configuration","url":"https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/configuring-ire.html?contentId=Qy3dDh~jSw5JICJGU2x7zg","note":"Record identification and update-authority principles; does not prescribe physical relabeling.","scope":"Record identification and update-authority principles; does not prescribe physical relabeling.","canonicalUrl":"https://datacenterlabeling.com/references/s02","markdownUrl":"https://datacenterlabeling.com/references/s02.md","guideSlugs":["duplicate-identifiers","facility-equipment-name-crosswalk","label-record-reconciliation"]},{"id":"S03","title":"Panduit: Infrastructure identification guide","url":"https://www.panduit.com/content/dam/panduit/en/website/solutions/documents/data-center-id-infrastructure0.pdf","note":"July 2014 historical rack-location examples; not current standards authority.","scope":"July 2014 historical rack-location examples; not current standards authority.","canonicalUrl":"https://datacenterlabeling.com/references/s03","markdownUrl":"https://datacenterlabeling.com/references/s03.md","guideSlugs":["rack-wayfinding","grounding-bonding-identification"],"reviewedAt":"2026-09-12"},{"id":"S04","title":"NetBox: Device model","url":"https://netbox.readthedocs.io/en/stable/models/dcim/device/","note":"Product-specific face and position semantics; local elevation translation is editorial guidance.","scope":"Product-specific face and position semantics; local elevation translation is editorial guidance.","canonicalUrl":"https://datacenterlabeling.com/references/s04","markdownUrl":"https://datacenterlabeling.com/references/s04.md","guideSlugs":["rack-face-and-u-position","asset-versus-location"]},{"id":"S05","title":"Corning: Labeling and documentation","url":"https://www.corning.com/catalog/coc/documents/brochures/LAN-1808-AEN.pdf","note":"January 2015 historical local/remote label examples; does not authorize service interruption.","scope":"January 2015 historical local/remote label examples; does not authorize service interruption.","canonicalUrl":"https://datacenterlabeling.com/references/s05","markdownUrl":"https://datacenterlabeling.com/references/s05.md","guideSlugs":["cable-endpoint-identification"]},{"id":"S06","title":"Brady: Patch-panel label creation","url":"https://support.bradyid.com/articles/en_US/Knowledge/How-to-Create-a-Basic-Patch-Panel-Label-in-Brady-Workstation","note":"Product-specific spacing and grouping inputs; all sample dimensions are fictional.","scope":"Product-specific spacing and grouping inputs; all sample dimensions are fictional.","canonicalUrl":"https://datacenterlabeling.com/references/s06","markdownUrl":"https://datacenterlabeling.com/references/s06.md","guideSlugs":["patch-panel-port-mapping"]},{"id":"S07","title":"Corning: EDGE procedure","url":"https://www.corning.com/catalog/coc/documents/standard-recommended-procedures/S46998-A0007-P146_EN.pdf","note":"Corning EDGE procedure S46998-A0007-P146, Issue 1, §§5.1–5.2, pages 19–23. Cover says December 2021; interior recordkeeping pages say February 2022. Equipment-specific hierarchy examples; mapping does not establish polarity.","scope":"Corning EDGE procedure S46998-A0007-P146, Issue 1, §§5.1–5.2, pages 19–23. Cover says December 2021; interior recordkeeping pages say February 2022. Equipment-specific hierarchy examples; mapping does not establish polarity.","canonicalUrl":"https://datacenterlabeling.com/references/s07","markdownUrl":"https://datacenterlabeling.com/references/s07.md","guideSlugs":["fiber-trunk-breakout-map"],"reviewedAt":"2026-09-12"},{"id":"S08","title":"Panduit: Cable labeling catalog","url":"https://www.panduit.com/content/dam/panduit/en/products/media/9/89/089/5089/110715089.pdf","note":"Marker capabilities are product-specific; proposed sample review makes no universal fit claim.","scope":"Marker capabilities are product-specific; proposed sample review makes no universal fit claim.","canonicalUrl":"https://datacenterlabeling.com/references/s08","markdownUrl":"https://datacenterlabeling.com/references/s08.md","guideSlugs":["dense-rack-label-visibility","label-fit-and-readability"]},{"id":"S09","title":"NVIDIA: Cable staging","url":"https://docs.nvidia.com/dgx-superpod/design-guide-cabling-data-centers/latest/stage.html","note":"DGX SuperPOD staging guidance, updated November 19, 2025; this worksheet covers identity reconciliation only.","scope":"DGX SuperPOD staging guidance, updated November 19, 2025; this worksheet covers identity reconciliation only.","canonicalUrl":"https://datacenterlabeling.com/references/s09","markdownUrl":"https://datacenterlabeling.com/references/s09.md","guideSlugs":["gpu-cable-staging"]},{"id":"S10","title":"Raritan: Advanced engineering","url":"https://www.raritan.com/eu/landing/raritan-advanced-engineering","note":"Manufacturer A/B differentiation example; no universal color code or proof of feed independence.","scope":"Manufacturer A/B differentiation example; no universal color code or proof of feed independence.","canonicalUrl":"https://datacenterlabeling.com/references/s10","markdownUrl":"https://datacenterlabeling.com/references/s10.md","guideSlugs":["a-b-power-feed-identification"]},{"id":"S11","title":"OSHA: 29 CFR 1910.303","url":"https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.303","note":"US workplace electrical marking provisions with applicability limits and exceptions; official indexed text checked September 12, 2026.","scope":"US workplace electrical marking provisions with applicability limits and exceptions; official indexed text checked September 12, 2026.","canonicalUrl":"https://datacenterlabeling.com/references/s11","markdownUrl":"https://datacenterlabeling.com/references/s11.md","guideSlugs":["panel-circuit-disconnect-marking"]},{"id":"S12","title":"NetBox: Power outlets","url":"https://netbox.readthedocs.io/en/stable/models/dcim/poweroutlet/","note":"Software record model for outlet identity and relationships; not a prescribed physical label format.","scope":"Software record model for outlet identity and relationships; not a prescribed physical label format.","canonicalUrl":"https://datacenterlabeling.com/references/s12","markdownUrl":"https://datacenterlabeling.com/references/s12.md","guideSlugs":["pdu-outlet-psu-map"]},{"id":"S13","title":"OSHA: 29 CFR 1910.145","url":"https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.145","note":"US accident-prevention signs and tags; operational identifiers have a different function.","scope":"US accident-prevention signs and tags; operational identifiers have a different function.","canonicalUrl":"https://datacenterlabeling.com/references/s13","markdownUrl":"https://datacenterlabeling.com/references/s13.md","guideSlugs":["operational-versus-safety-labels"]},{"id":"S14","title":"OSHA: 29 CFR 1910.333","url":"https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.333","note":"US electrical work practices; identification records do not establish an electrically safe work condition.","scope":"US electrical work practices; identification records do not establish an electrically safe work condition.","canonicalUrl":"https://datacenterlabeling.com/references/s14","markdownUrl":"https://datacenterlabeling.com/references/s14.md","guideSlugs":["a-b-power-feed-identification","operational-versus-safety-labels"]},{"id":"S15","title":"ASME: A13.1 piping identification","url":"https://www.asme.org/codes-standards/find-codes-standards/a13-1-scheme-identification-piping-systems","note":"Public scope overview only; no complete color or placement specification was accessed.","scope":"The publisher overview describes identification of fluids in aboveground piping and excludes electrical conduits. It displays A13.1-2026 at the September 12, 2026 review. The overview does not supply the full color, size or placement requirements; project applicability requires the adopted text.","canonicalUrl":"https://datacenterlabeling.com/references/s15","markdownUrl":"https://datacenterlabeling.com/references/s15.md","guideSlugs":["cooling-pipe-identification"],"reviewedAt":"2026-09-12"},{"id":"S16","title":"Lenovo: N1380 manifold instructions","url":"https://pubs.lenovo.com/n1380/install_the_manifold","note":"N1380-specific hose and manifold identification context; its colors, routing, and procedures do not apply universally.","scope":"N1380-specific hose and manifold identification context; its colors, routing, and procedures do not apply universally.","canonicalUrl":"https://datacenterlabeling.com/references/s16","markdownUrl":"https://datacenterlabeling.com/references/s16.md","guideSlugs":["liquid-cooling-hose-endpoints","facility-equipment-name-crosswalk"]},{"id":"S17","title":"Vertiv: Liebert XD system design manual","url":"https://www.vertiv.com/49f56b/globalassets/shared/liebert-xd-system-design-manual_00.pdf","note":"Liebert XD system design manual SL-16655_REV17_08-24, §3.11, printed pages 24–25 (PDF pages 30–31). Equipment-specific supply/return context; does not prescribe a BMS crosswalk.","scope":"Liebert XD system design manual SL-16655_REV17_08-24, §3.11, printed pages 24–25 (PDF pages 30–31). Equipment-specific supply/return context; does not prescribe a BMS crosswalk.","canonicalUrl":"https://datacenterlabeling.com/references/s17","markdownUrl":"https://datacenterlabeling.com/references/s17.md","guideSlugs":["facility-equipment-name-crosswalk"],"reviewedAt":"2026-09-12"},{"id":"S18","title":"Smithsonian: Design standards, volume 2","url":"https://www.wbdg.org/FFC/SI/si_sds_vol2.pdf","note":"October 2021 owner specification; communications as-built requirements at printed section 27 15 00-4. Not a universal mandate.","scope":"The Smithsonian specification is an owner-specific example of required documentation and review. Rackstamp’s suggested handoff wording is original editorial language, not a quoted contractual requirement.","canonicalUrl":"https://datacenterlabeling.com/references/s18","markdownUrl":"https://datacenterlabeling.com/references/s18.md","guideSlugs":["pathway-route-identification","contractor-labeling-handoff"],"reviewedAt":"2026-09-12"},{"id":"S19","title":"Equinix: Cross-connect demarcations","url":"https://docs.equinix.com/cross-connect/installation/xc-demarcations/","note":"Provider-specific demarcation and customer onward-patching context; consult the actual service arrangement.","scope":"Provider-specific demarcation and customer onward-patching context; consult the actual service arrangement.","canonicalUrl":"https://datacenterlabeling.com/references/s19","markdownUrl":"https://datacenterlabeling.com/references/s19.md","guideSlugs":["colocation-demarcation"]},{"id":"S20","title":"Equinix: Ordering a cross connect with an LOA","url":"https://docs.equinix.com/cross-connect/ordering/xc-order-cc-with-loa/","note":"Provider-specific authorization and ordering context. A worksheet neither authorizes nor orders service.","scope":"Provider-specific authorization and ordering context. A worksheet neither authorizes nor orders service.","canonicalUrl":"https://datacenterlabeling.com/references/s20","markdownUrl":"https://datacenterlabeling.com/references/s20.md","guideSlugs":["colocation-demarcation"]},{"id":"S21","title":"Brady: Material selection guidance","url":"https://support.bradyid.com/articles/en_US/Knowledge/Brady-Material-Selection-Tool","note":"Manufacturer selection factors; no universal material approval or test duration. Checked September 12, 2026.","scope":"Manufacturer selection factors; no universal material approval or test duration. Checked September 12, 2026.","canonicalUrl":"https://datacenterlabeling.com/references/s21","markdownUrl":"https://datacenterlabeling.com/references/s21.md","guideSlugs":["label-material-failure","label-fit-and-readability"]},{"id":"S22","title":"Brady: Ribbon and label compatibility","url":"https://support.bradyid.com/articles/en_US/Knowledge/Ribbon-and-Label-Compatibility","note":"Manufacturer guidance on qualified combinations and print durability.","scope":"Manufacturer guidance on qualified combinations and print durability.","canonicalUrl":"https://datacenterlabeling.com/references/s22","markdownUrl":"https://datacenterlabeling.com/references/s22.md","guideSlugs":["label-print-quality","choosing-a-label-printer"]},{"id":"S23","title":"Zebra: Adjusting print quality","url":"https://docs.zebra.com/us/en/printers/desktop/zd421-and-zd621-desktop-printers-user-guide/print-operations/adjusting-the-print-quality.html","note":"ZD421/ZD621-specific guidance; settings are not universal.","scope":"ZD421/ZD621-specific guidance; settings are not universal.","canonicalUrl":"https://datacenterlabeling.com/references/s23","markdownUrl":"https://datacenterlabeling.com/references/s23.md","guideSlugs":["label-print-quality"]},{"id":"S24","title":"Brady: Spreadsheet import preparation","url":"https://support.bradyid.com/articles/en_US/Knowledge/How-to-format-Excel-files-for-importing-into-Brady-software","note":"Brady import behavior and text preparation; the batch accounting workflow is editorial.","scope":"Brady import behavior and text preparation; the batch accounting workflow is editorial.","canonicalUrl":"https://datacenterlabeling.com/references/s24","markdownUrl":"https://datacenterlabeling.com/references/s24.md","guideSlugs":["bulk-label-import"]},{"id":"S25","title":"Zebra: Barcode input documentation","url":"https://techdocs.zebra.com/datawedge/11-1/guide/input/barcode/","note":"DataWedge 11.1 hardware, decoder, formatting, and quiet-zone context; payload/lookup workflow is editorial.","scope":"DataWedge 11.1 hardware, decoder, formatting, and quiet-zone context; payload/lookup workflow is editorial.","canonicalUrl":"https://datacenterlabeling.com/references/s25","markdownUrl":"https://datacenterlabeling.com/references/s25.md","guideSlugs":["barcode-qr-scan-quality"]},{"id":"S26","title":"Fluke Networks: Test and labeling documentation","url":"https://www.flukenetworks.com/blog/cabling-chronicles/your-burden-proof-lies-documentation","note":"Published February 16, 2016; supports label/document correspondence, not current-edition or technical acceptance claims.","scope":"Published February 16, 2016; supports label/document correspondence, not current-edition or technical acceptance claims.","canonicalUrl":"https://datacenterlabeling.com/references/s26","markdownUrl":"https://datacenterlabeling.com/references/s26.md","guideSlugs":["cable-test-id-reconciliation","labeling-business-case"]},{"id":"S27","title":"IBM: Server cable management and labeling","url":"https://www.ibm.com/support/pages/cable-management-and-labeling-servers","note":"Replacement labels and documented deviations; migration workflow is editorial.","scope":"Replacement labels and documented deviations; migration workflow is editorial.","canonicalUrl":"https://datacenterlabeling.com/references/s27","markdownUrl":"https://datacenterlabeling.com/references/s27.md","guideSlugs":["moves-and-retirement-closeout"]},{"id":"S28","title":"NIST: SP 800-88 Revision 2","url":"https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-88r2.pdf","note":"September 2025; device/media identity in disposition evidence. No sanitization procedure reproduced.","scope":"September 2025; device/media identity in disposition evidence. No sanitization procedure reproduced.","canonicalUrl":"https://datacenterlabeling.com/references/s28","markdownUrl":"https://datacenterlabeling.com/references/s28.md","guideSlugs":["moves-and-retirement-closeout"]},{"id":"S29","title":"Sunbird: Asset audit application note","url":"https://www.sunbirddcim.com/sites/default/files/AN011_Sunbird_Application_Note_Asset_Audit_0.pdf","note":"Manufacturer audit-log example; frequency, sampling, and closure workflow here are editorial.","scope":"Manufacturer audit-log example; frequency, sampling, and closure workflow here are editorial.","canonicalUrl":"https://datacenterlabeling.com/references/s29","markdownUrl":"https://datacenterlabeling.com/references/s29.md","guideSlugs":["label-audit-evidence"]},{"id":"S30","title":"TIA-606-E recirculation ballot notice","url":"https://tiaonline.org/standardannouncement/tia-issues-a-recirculation-ballot-and-public-review-notification-for-tia-606-e-administration-standard-for-telecommunications-infrastructure-2/","note":"TIA's June 19, 2026 recirculation-ballot and public-review notice for TIA-606-E. It establishes the notice's stage and date, not final publication or project adoption.","scope":"This publisher notice confirms that TIA issued a ballot and call for comments for TIA-606-E on June 19, 2026. Read it as evidence of that event. It is not the full standard, a final-publication announcement, or a naming scheme for a particular site.","canonicalUrl":"https://datacenterlabeling.com/references/s30","markdownUrl":"https://datacenterlabeling.com/references/s30.md","guideSlugs":["labeling-standards-and-project-requirements"],"reviewedAt":"2026-09-12"},{"id":"S31","title":"TIA-942 official overview","url":"https://tiaonline.org/standard/tia-942/","note":"TIA's official TIA-942 overview lists Revision C, published May 2024, and describes data-center infrastructure scope. It does not supply a local cable-label naming policy.","scope":"The publisher page identifies TIA-942 Revision C and a May 2024 publication date. Its overview concerns data-center and computer-room infrastructure. Use the project's adopted documents for detailed requirements and the site's controlled policy for local identifier syntax.","canonicalUrl":"https://datacenterlabeling.com/references/s31","markdownUrl":"https://datacenterlabeling.com/references/s31.md","guideSlugs":["labeling-standards-and-project-requirements"],"reviewedAt":"2026-09-12"},{"id":"S32","title":"NIST: SP 800-53 official control catalogue, PE-10","url":"https://csrc.nist.gov/CSRC/media/Projects/risk-management/800-53%20Downloads/800-53r5/SP_800-53_v5_1-derived-OSCAL.pdf","note":"Official catalogue scope for emergency shutoff; local labeling record and change triggers are editorial, with no functional operation procedure.","scope":"NIST PE-10 addresses emergency shutoff capability, organization-defined access, and protection from unauthorized activation. It does not provide a universal label legend or authorize a functional test during an identification survey.","canonicalUrl":"https://datacenterlabeling.com/references/s32","markdownUrl":"https://datacenterlabeling.com/references/s32.md","guideSlugs":["panel-circuit-disconnect-marking"],"reviewedAt":"2026-09-12"},{"id":"S33","title":"NFPA: NFPA 70E, 2024 official publication","url":"https://link.nfpa.org/all-publications/70E/2024","note":"Publication and scope reference; no detailed clause, fixed sticker-expiry interval, PPE advice, or calculated electrical result reproduced.","scope":"The publication reference identifies the NFPA 70E edition used for context. Technical applicability and the content of an equipment marking require the responsible electrical review and appropriate controlled documentation.","canonicalUrl":"https://datacenterlabeling.com/references/s33","markdownUrl":"https://datacenterlabeling.com/references/s33.md","guideSlugs":["operational-versus-safety-labels"],"reviewedAt":"2026-09-12"},{"id":"S34","title":"NFPA: Energy Storage Systems fact sheet","url":"https://www.nfpa.org/-/media/project/storefront/catalog/files/code-or-topic-fact-sheets/ESSFactSheet.pdf","note":"Official February 2024 overview referring to NFPA 855's cited edition. Technology-specific sign wording and applicability remain with the responsible reviewer.","scope":"The NFPA fact sheet is introductory context for stationary energy storage. It does not determine the required sign set for a particular battery technology, equipment arrangement, or jurisdiction.","canonicalUrl":"https://datacenterlabeling.com/references/s34","markdownUrl":"https://datacenterlabeling.com/references/s34.md","guideSlugs":["operational-versus-safety-labels"],"reviewedAt":"2026-09-12"},{"id":"S35","title":"NetBox Labs: NetBox 4.4 customization","url":"https://netboxlabs.com/docs/netbox/v4.4/features/customization/","note":"Versioned export-capability context; proposed output schema and reconciliation controls are editorial.","scope":"Versioned export-capability context; proposed output schema and reconciliation controls are editorial.","canonicalUrl":"https://datacenterlabeling.com/references/s35","markdownUrl":"https://datacenterlabeling.com/references/s35.md","guideSlugs":["label-record-reconciliation"]},{"id":"S36","title":"NetBox Labs: NetBox 4.4 export templates","url":"https://netboxlabs.com/docs/netbox/v4.4/customization/export-templates/","note":"Object-type-specific export templates and rendering context. Local field names, template revisions, and required-data handling must be mapped to the actual installation.","scope":"NetBox 4.4 documentation supports the described export-template capability and object-type context. A particular installation still needs its own schema, permissions, selection scope, and acceptance checks.","canonicalUrl":"https://datacenterlabeling.com/references/s36","markdownUrl":"https://datacenterlabeling.com/references/s36.md","guideSlugs":["label-record-reconciliation"],"reviewedAt":"2026-09-12"},{"id":"S37","title":"UL Solutions: Marking and labeling systems FAQs","url":"https://www.ul.com/resources/marking-and-labeling-systems-faqs","note":"Conditions of acceptability, specified printing combinations, and permanence-only evaluation scope. Checked September 12, 2026.","scope":"UL explains that recognition has application and printing conditions. Its permanence evaluation is distinct from separate flammability, electrical, or structural ratings.","canonicalUrl":"https://datacenterlabeling.com/references/s37","markdownUrl":"https://datacenterlabeling.com/references/s37.md","guideSlugs":["label-material-failure"],"reviewedAt":"2026-09-12"},{"id":"S38","title":"UL Solutions: UL 969A certification scope","url":"https://www.ul.com/news/ul-offers-certification-services-new-marking-and-labeling-standard-ul-969a","note":"March 24, 2021 scope announcement; no universal data-center requirement inferred.","scope":"UL describes a specific scope for flag labels, flag tags, wrap-around labels, and related products. Applicability depends on the marking system and end-product application.","canonicalUrl":"https://datacenterlabeling.com/references/s38","markdownUrl":"https://datacenterlabeling.com/references/s38.md","guideSlugs":["label-material-failure"],"reviewedAt":"2026-09-12"},{"id":"S39","title":"Brady: B-438 technical data sheet","url":"https://tds.bradyid.com/TDSdocs/B-438.pdf","note":"Sheet dated 10/05/2022; product-specific checkerboard tamper-function limitation and stated R4300/aluminum sample construction. Not a universal material or service-temperature rule.","scope":"The cited data sheet describes a particular material and its tamper-indicating function under specified conditions. Its limits are not a universal rule for tamper-evident labels.","canonicalUrl":"https://datacenterlabeling.com/references/s39","markdownUrl":"https://datacenterlabeling.com/references/s39.md","guideSlugs":["label-material-failure"],"reviewedAt":"2026-09-12"},{"id":"S40","title":"Cloudflare: Dashboard and API outage on April 15, 2020","url":"https://blog.cloudflare.com/cloudflare-dashboard-and-api-outage-on-april-15-2020/","note":"Primary operator incident report published April 16, 2020. Scope limited to the reported event; retirement-register lesson is explicitly editorial.","scope":"Cloudflare describes the April 15, 2020 Dashboard and API outage and its restoration and prevention measures. Its customer-traffic proxying continued; the case is not a claim that its entire network stopped or that labeling was the sole cause.","canonicalUrl":"https://datacenterlabeling.com/references/s40","markdownUrl":"https://datacenterlabeling.com/references/s40.md","guideSlugs":["moves-and-retirement-closeout","legacy-room-relabeling"],"reviewedAt":"2026-09-12"},{"id":"S41","title":"TIA: ANSI/TIA-607-E publication announcement","url":"https://tiaonline.org/standardannouncement/tia-publishes-new-standard-ansi-tia-607-e-generic-telecommunications-bonding-and-grounding-earthing-for-customer-premises/","note":"Primary May 17, 2024 publication announcement. Establishes E publication, not project adoption or detailed clause changes. Checked September 12, 2026.","scope":"TIA announced publication of ANSI/TIA-607-E on May 17, 2024. The announcement describes the revision; a project requirement still needs the applicable adopted text.","canonicalUrl":"https://datacenterlabeling.com/references/s41","markdownUrl":"https://datacenterlabeling.com/references/s41.md","guideSlugs":["grounding-bonding-identification"],"reviewedAt":"2026-09-12"},{"id":"S42","title":"Zebra: Direct thermal and thermal transfer printing","url":"https://www.zebra.com/us/en/resource-library/faq/difference-between-direct-thermal-and-thermal-transfer-printing.html","note":"Primary manufacturer explanation of the two printing processes and the importance of intended exposure and material/ribbon matching. Used for those limited facts; no model ranking, universal durability claim, or vendor performance figure adopted.","scope":"Primary manufacturer explanation of the two printing processes and the importance of intended exposure and material/ribbon matching. Used for those limited facts; no model ranking, universal durability claim, or vendor performance figure adopted.","canonicalUrl":"https://datacenterlabeling.com/references/s42","markdownUrl":"https://datacenterlabeling.com/references/s42.md","guideSlugs":["choosing-a-label-printer"]},{"id":"S43","title":"Impinj: How RAIN RFID systems work","url":"https://www.impinj.com/products/technology/how-do-rain-rfid-systems-work","note":"Primary technical explanation of passive RAIN tags, readers and software, non-line-of-sight reading, and the relevance of metal and liquids. No advertised range, rate, cost, accuracy or efficiency claim adopted.","scope":"Primary technical explanation of passive RAIN tags, readers and software, non-line-of-sight reading, and the relevance of metal and liquids. No advertised range, rate, cost, accuracy or efficiency claim adopted.","canonicalUrl":"https://datacenterlabeling.com/references/s43","markdownUrl":"https://datacenterlabeling.com/references/s43.md","guideSlugs":["rfid-aim-or-barcodes"]},{"id":"S44","title":"GS1: RFID read range","url":"https://support.gs1.org/support/solutions/articles/43000734166-what-is-the-read-range-for-a-typical-rfid-tag-","note":"Primary standards-organization support guidance that read range and read volume depend on system and environmental factors, including orientation. Used to support a measured local read-zone pilot, not a guaranteed distance.","scope":"Primary standards-organization support guidance that read range and read volume depend on system and environmental factors, including orientation. Used to support a measured local read-zone pilot, not a guaranteed distance.","canonicalUrl":"https://datacenterlabeling.com/references/s44","markdownUrl":"https://datacenterlabeling.com/references/s44.md","guideSlugs":["rfid-aim-or-barcodes"]},{"id":"S45","title":"CommScope: Automated infrastructure management fact file","url":"https://www.commscope.com/insights/the-enterprise-source/automated-infrastructure-management-aim-the-fact-file/","note":"Primary manufacturer explanation of one AIM implementation with intelligent panels, controllers and management software. Supports the distinction between connection observations and general inventory; capabilities must be qualified for the selected system.","scope":"Primary manufacturer explanation of one AIM implementation with intelligent panels, controllers and management software. Supports the distinction between connection observations and general inventory; capabilities must be qualified for the selected system.","canonicalUrl":"https://datacenterlabeling.com/references/s45","markdownUrl":"https://datacenterlabeling.com/references/s45.md","guideSlugs":["rfid-aim-or-barcodes"]},{"id":"S46","title":"ISO/IEC 18598:2016 publisher record","url":"https://www.iso.org/standard/62987.html","note":"Publisher scope record for the AIM requirements/data-exchange standard. Only scope is cited; no full-text clause, conformance judgment or universal interface capability inferred.","scope":"Publisher scope record for the AIM requirements/data-exchange standard. Only scope is cited; no full-text clause, conformance judgment or universal interface capability inferred.","canonicalUrl":"https://datacenterlabeling.com/references/s46","markdownUrl":"https://datacenterlabeling.com/references/s46.md","guideSlugs":["rfid-aim-or-barcodes"]},{"id":"S47","title":"W3C: Understanding Success Criterion 1.4.1 Use of Color","url":"https://www.w3.org/WAI/WCAG22/Understanding/use-of-color.html","note":"Primary web-accessibility guidance. The physical-marker reading check is an explicitly editorial application, not a physical-label compliance claim.","scope":"Primary web-accessibility guidance. The physical-marker reading check is an explicitly editorial application, not a physical-label compliance claim.","canonicalUrl":"https://datacenterlabeling.com/references/s47","markdownUrl":"https://datacenterlabeling.com/references/s47.md","guideSlugs":["cable-color-legends"]},{"id":"S48","title":"UL: Marking and Labeling Systems Program","url":"https://www.ul.com/services/marking-and-labeling-systems-program","note":"Recognition categories and conditions of acceptability depend on the evaluated construction and end-use conditions.","scope":"Recognition categories and conditions of acceptability depend on the evaluated construction and end-use conditions.","canonicalUrl":"https://datacenterlabeling.com/references/s48","markdownUrl":"https://datacenterlabeling.com/references/s48.md","guideSlugs":["labeling-standards-and-project-requirements"]},{"id":"S49","title":"Brother: Cut options in iPrint&Label","url":"https://help.brother-usa.com/app/answers/detail/a_id/183293/~/cut-options---iprint%26label","note":"Primary manufacturer support page checked for named cut/feed options and model-dependent half-cut availability. No device recommendation, universal margin or cutter setting is adopted.","scope":"Primary manufacturer support page checked for named cut/feed options and model-dependent half-cut availability. No device recommendation, universal margin or cutter setting is adopted.","canonicalUrl":"https://datacenterlabeling.com/references/s49","markdownUrl":"https://datacenterlabeling.com/references/s49.md","guideSlugs":["bulk-label-import"],"reviewedAt":"2026-09-12"}],"topics":[{"title":"Naming and location labels","description":"Choose the right starting point for data center naming, duplicate IDs, rack wayfinding, rack-unit positions, and asset moves, with evidence for a clear closeout.","canonicalUrl":"https://datacenterlabeling.com/topics/naming-location","markdownUrl":"https://datacenterlabeling.com/topics/naming-location.md"},{"title":"Cable labeling and connection maps","description":"Find the right guide for cable-end labels, patch-panel ports, fiber breakouts, dense-bundle visibility, and GPU cable kits. Keep identity and technical checks distinct.","canonicalUrl":"https://datacenterlabeling.com/topics/cable-labeling","markdownUrl":"https://datacenterlabeling.com/topics/cable-labeling.md"},{"title":"Power identification and safety labels","description":"Select the right identification guide for A/B feeds, circuits, PDU outlets, bonding, and safety labels. Record uncertainties for the responsible electrical owner.","canonicalUrl":"https://datacenterlabeling.com/topics/power-safety-labels","markdownUrl":"https://datacenterlabeling.com/topics/power-safety-labels.md"},{"title":"Cooling and facility labels","description":"Connect pipe markers, cooling hoses, BMS names, cable pathways, and colo handoffs to their exact records, equipment references, and responsibility boundaries.","canonicalUrl":"https://datacenterlabeling.com/topics/cooling-facility-labels","markdownUrl":"https://datacenterlabeling.com/topics/cooling-facility-labels.md"},{"title":"Label materials, printing, and scanning","description":"Diagnose peeling, poor fit, print defects, damaged imports, and failed scans. Qualify the exact label application and compare accepted output before buying equipment.","canonicalUrl":"https://datacenterlabeling.com/topics/label-materials-printing","markdownUrl":"https://datacenterlabeling.com/topics/label-materials-printing.md"},{"title":"Labeling records, handoffs, and audits","description":"Resolve label-record conflicts, preserve cable-test identities, accept contractor handoffs, close moves and retirements, and document the actual scope of label audits.","canonicalUrl":"https://datacenterlabeling.com/topics/labeling-records-audits","markdownUrl":"https://datacenterlabeling.com/topics/labeling-records-audits.md"}]}