Find the next useful step.

ROUTE 01

An incident exposed an uncertain label

Use the incident process to stabilize the service. For the subsequent identification review, capture the observed label and the conflicting record before replacing either. Start with the affected connection, then check the records and change closeout.

1. I cannot identify the other cable end
2. A and B feeds are easy to confuse
3. The supplying circuit or disconnect is unclear
4. PDU outlets cannot be matched to device power supplies
5. The physical label and system record disagree
6. Moves and retirements leave stale labels behind

Finish with a reviewed correction and retained evidence; a new label alone does not establish the cause of the incident.

ROUTE 02

An audit is approaching

Define the audit population and the evidence being requested before counting tags. Compare expected assets with observations, retain discrepancies, and make the sample selection reproducible.

1. Moving a device makes its identity confusing
2. The physical label and system record disagree
3. No one can prove labels were checked

Finish with a bounded conclusion: what was checked, against which criteria, which exceptions remain, and who accepted closure.

ROUTE 03

We are commissioning a new room

Agree identifiers and responsibility before printing. Prove a small rack, panel, cable, and power-label set against the same records; use that accepted example to define the handoff package.

1. We do not have a naming convention
2. I cannot find the correct rack
3. Patch-panel and port labels do not match
4. PDU outlets cannot be matched to device power supplies
5. Contractor handoffs leave inconsistent labels

Finish with an approved local convention, a physical print proof, and matching records that the operating team can maintain.

ROUTE 04

I inherited a room with uncertain records

Establish a room and rack baseline, reserve identifiers, and separate observed relationships from assumptions. Plan manageable work packages around approved access and change windows.

Plan a legacy-room relabeling program ↗

1. We do not have a naming convention
2. Two objects have the same ID
3. I cannot find the correct rack
4. I cannot identify the other cable end
5. The physical label and system record disagree
6. Moves and retirements leave stale labels behind

Finish each package with reconciled evidence before expanding its scope. Calendar dates do not override unresolved identification or access constraints.

ROUTE 05

Labels keep failing or cannot be read

Record the failed material, surface, application conditions, and print setup. Determine whether the issue is adhesion, placement, contrast, symbol size, or an incorrect label format.

1. Labels disappear inside dense bundles
2. Labels peel, fade, or fail in service
3. The label does not fit or the text is too small
4. Print smears, clips, or shifts
5. A barcode or QR code will not scan reliably

Finish with an applied sample checked under the intended reading conditions and a reproducible setup for replacement batches.

ROUTE 06

We are choosing printers or automation

Describe the actual labels and records first. Compare printers on accepted output and total operating costs. Compare barcodes, RFID, and AIM on the different observations each system can supply.

Choose a label printer for the work you actually do ↗ · Choose barcodes, RFID, or AIM for the evidence you need ↗

1. Labels peel, fade, or fail in service
2. The label does not fit or the text is too small
3. Bulk imports corrupt or duplicate identifiers
4. A barcode or QR code will not scan reliably
5. The physical label and system record disagree

Finish with a documented pilot, explicit acceptance criteria, and ownership of exceptions and integrations.

ROUTE 07

Several sites or contractors need one approach

Agree the scope of uniqueness, maintain a prefix register, and state which local conventions may differ. Set a mapping and retirement process for inherited names rather than silently renumbering every object.

Create a cable-color legend people can use ↗

1. We do not have a naming convention
2. Two objects have the same ID
3. Carrier, colo, and tenant circuit IDs disagree
4. Contractor handoffs leave inconsistent labels

Finish with versioned policy, ownership boundaries, and acceptance evidence that follows each object across teams.

ROUTE 08

A GPU or liquid-cooling hall is coming online

Keep installation sequence, actual assembly endpoints, facility names, and operational identifiers connected. Coordinate the IT and facilities records with the approved manufacturer and design documentation.

1. Fiber trunks and breakout legs are ambiguous
2. GPU cable bundles lose their installation sequence
3. A and B feeds are easy to confuse
4. Cooling pipe supply, return, or flow is unclear
5. Liquid-cooling hoses lose their endpoint identity
6. Facility equipment names do not match alarm names

Finish with clear endpoint mappings, accessible identifiers, and a crosswalk from equipment labels to facility alarms.

ROUTE 09

The labeling project needs a budget

Measure current tracing, reprint, and reconciliation work. Separate cash expenditure from staff time, and compare conservative scenarios using the same scope and units.

Build a labeling budget and business case ↗

1. Labels peel, fade, or fail in service
2. Bulk imports corrupt or duplicate identifiers
3. Contractor handoffs leave inconsistent labels
4. No one can prove labels were checked

Finish with a measurable pilot and a business case that identifies assumptions, recurring costs, and the evidence needed to continue.