Field work
We do not have a naming convention
- Must every ID contain its location?
- Should we relabel everything immediately?
- Who should approve the convention?
- Can we keep a useful legacy abbreviation?
- What belongs in a naming-policy exception?
- Should rack numbers restart in every hall?
- Should we number cabinets sequentially or by floor tile?
- How many digits should a rack number have?
- Can the rack identifier also be the server's host name?
- Which letters should we skip in row identifiers?
- Does upper and lower case matter in an identifier?
- Where should the numbering start in a row?
- Can we put the customer or tenant name in a colocation cabinet identifier?
Two objects have the same ID
I cannot find the correct rack
Front, rear, and rack units disagree
Moving a device makes its identity confusing
I cannot identify the other cable end
- Can the cable ID alone be enough?
- What if the remote end cannot be confirmed?
- Which cable-labeling format is best?
- Can we label only the end that changed?
- What should an unresolved destination label say?
- How many characters fit on a cable label?
- Should the label show both endpoints or only the far one?
- Does TIA-606 require a label within twelve inches of the termination?
- Why does the same information reversed not work at both ends?
- The correct text does not fit the cable. What are the options?
- Why is the legend only readable from one side?
- Can a cable be too thin to wrap?
- Does a correct label at both ends mean the link works?
Patch-panel and port labels do not match
- Should the new label replace factory numbers?
- The numbering is right but the strip still drifts. What next?
- What size should a patch-panel label be?
- Can I prepare the source in Excel?
- Does a standards reference provide a universal numbering template?
- Are patch panel ports numbered left to right?
- Should the patch panel label show the port number or where the cable goes?
- What is a 24-port patch panel label template?
- Do I have to relabel a panel that already has port numbers printed on it?
- How do I label a 48-port panel that is numbered in two rows?
- What goes on the back of a patch panel?
- How should fiber cassette ports be identified?
- Which TIA-606 administration class applies to a data center patch panel?
Fiber trunks and breakout legs are ambiguous
- Can the jacket or connector color identify the correct leg?
- How should spare fibers appear?
- Is there a universal fiber numbering diagram we can copy?
- Should unused legs disappear from the label register?
- Can we close identity mapping while a polarity record is pending?
- What is the difference between MPO and MTP?
- How many duplex ports does one MPO connector become?
- Which polarity method should the label show?
- Is a fiber patch panel labeled the same way as a copper patch panel?
- Should a cassette have its own identifier?
- What does base-8 or base-12 mean for the port register?
- Is TIA-568.3-D still the current optical fiber components standard?
- How should the rear of a fiber panel be labeled?
Labels disappear inside dense bundles
GPU cable bundles lose their installation sequence
A and B feeds are easy to confuse
- Should A always be one particular color?
- Can a matching record prove two feeds are independent?
- Can a PDU position be printed on the same face as its feed name?
- What if the sticker says A but the legend says FEED A?
- Can I finish the readable PDUs while one remains uncertain?
- Does an old photo remain useful after replacement?
The supplying circuit or disconnect is unclear
PDU outlets cannot be matched to device power supplies
Grounding and bonding connections cannot be traced
- Can I assign a new busbar name during the survey?
- Does a complete register demonstrate a good bond?
- Can a rack location stand in for an equipment endpoint?
- What if the busbar has no numbered positions?
- Can a renamed busbar keep its old alias in search records?
- Should electrical inspection evidence be copied into this register?
Asset stickers and safety labels get mixed up
- Can one sticker carry both an asset ID and a warning?
- Does this checklist tell me which warning is required?
- How should I record a label whose function is unknown?
- Can I use a neighboring unit's warning as a replacement model?
- Does moving the asset sticker automatically close the safety finding?
- What should a final photograph include?
Cooling pipe supply, return, or flow is unclear
Liquid-cooling hoses lose their endpoint identity
Facility equipment names do not match alarm names
Cable pathways cannot be matched to drawings
- Should the whole route have one ID or many?
- Can I fill a concealed section from the drawing?
- How do I record a junction with two successors?
- Can a penetration label replace a firestop reference?
- What if the pathway exists but is missing from the drawing?
- Does a reversible route check prove the cable route?
Carrier, colo, and tenant circuit IDs disagree
- Must the carrier and tenant use the same circuit name?
- Does the completed worksheet authorize a cross-connect?
- What if the tenant nickname stays the same during a migration?
- Can I swap A and Z to match my local drawing?
- Is a matched demarcation enough to close the onward patch?
- Should I delete a superseded LOA from the working history?
Labels peel, fade, or fail in service
The label does not fit or the text is too small
Print smears, clips, or shifts
Bulk imports corrupt or duplicate identifiers
A barcode or QR code will not scan reliably
The physical label and system record disagree
Test results use different cable IDs
Contractor handoffs leave inconsistent labels
Moves and retirements leave stale labels behind
No one can prove labels were checked
Identify cooling valves and isolation points
- Does tagging a valve establish an isolation point for work?
- Should the tag name the valve or what it isolates?
- What if a valve in the field is missing from the schedule?
- Can one tag cover a pair of valves isolating the same segment?
- How should a bypass around a valve be recorded?
- Does a normal position in the record mean the valve is in that position now?
Separate cooling loops and the units that serve them
- Why record the facility loop and technology loop separately?
- Can the monitoring system's loop name be the record?
- Should the served set list every rack individually?
- How should an N+1 arrangement be recorded?
- What if one rack appears under two units?
- Does this register establish that a unit can cool its served set?
Nobody can tell which tap-off box feeds which rack
- Should the label on the box name the rack it feeds?
- What if our tap-off boxes are not in the asset register at all?
- Can we relabel a box in the field when we find it wrong?
- Is a tap-off box covered by the same standard as the busway?
- How do we identify an empty tap position?
- The busway was installed by a different contractor. Whose labels are these?
- If the box identifier says nothing about the load, how does anyone find the right box at 2am?
- Do we need to mark a position that has never had a box on it?
- Our positions were renumbered after a removal. What now?
- Can the survey tell us whether a box is correctly rated for what it feeds?
- The busway housing is dirty and the run marking is unreadable. Is that a labeling finding?
- Should tap-off boxes be in the asset register or treated as parts of the run?
- Who owns busway labels when the busway came with the building?
Planning and decisions
Choose a label printer for the work you actually do
Choose barcodes, RFID, or AIM for the evidence you need
Create a cable-color legend people can use
Plan a legacy-room relabeling program
Build a labeling budget and business case
Data center labeling standards: build a project requirements map
- Can one standard cover all data center labels?
- Is a publisher webpage enough to verify a clause?
- Should we rename everything when an edition changes?
- Does a successful print proof establish compliance?
- What should a contractor submit before labeling starts?
- Is TIA-606 mandatory for a data center?
- Which class of administration does a data center need?
- Is TIA-606-B still current?
- What is the current edition of TIA-606?
- Does TIA-606 cover IT asset tags?
- Does TIA-606 tell me what to print on a label?
- Which standard covers chilled-water pipe labels?
- Is TIA-942 a labeling standard?
- Which document covers automated infrastructure management data?
- How many standards should a labeling specification name?
Check arc flash and electrical safety labels against their source
- Can we print a replacement arc flash label ourselves?
- The label has no date. Is it still valid?
- Who sets the review interval?
- What if the equipment identifier on the label does not exist in our records?
- In a colocation space, whose label is it?
- Does a labeling audit demonstrate electrical safety compliance?
- What is the current edition of NFPA 70E?
- Does a new edition of NFPA 70E mean our labels are out of date?
- Is it the label or the arc flash study that gets reviewed on an interval?
- Does IEEE 1584 say which protective equipment to wear?
- Why do two labels on the same equipment show different incident energy?
- Is an arc flash label the same as an equipment nameplate?
- Can we cover or replace a manufacturer's nameplate with our own label?
- Which ANSI Z535 standard applies to a label on facility switchgear?
- Does every panel in the data hall need an arc flash label?
Prepare labeling evidence for an audit or assessment
Select label materials for the conditions at the label
Tag assets at intake so the register starts complete
Sign aisles and rows so a stranger finds the right face
- Should the sign say hot aisle and cold aisle?
- Do we need a temperature on the containment door?
- How large should the lettering be?
- Can we use color to distinguish the two faces?
- Who owns the aisle signs?
- Is any of this required by code?
- Which end of the row should we sign first if we can only afford one?
- Do we need an arrow if the numbering is obvious?
- Can we put the rack elevation or power feed on the row sign?
- How high should a row sign be?
- Who owns the row signs in a colocation hall?
Label the PCI DSS scope boundary so the room matches the diagram
- Does labeling put a system in or out of scope?
- Which version of PCI DSS should we map to?
- Can color alone carry the scope state?
- Our provider will not relabel their side of a cross-connect. What then?
- Should open exceptions be closed before the assessment?
- Is a photograph of a labeled cabinet sufficient evidence?