# Cooling and facility labels

> Connect pipe markers, cooling hoses, BMS names, cable pathways, and colo handoffs to their exact records, equipment references, and responsibility boundaries.

Canonical page: https://datacenterlabeling.com/topics/cooling-facility-labels

## Find the boundary the label describes

Facility identification often crosses boundaries between physical equipment, drawings, monitoring systems, and external providers. A pipe service name describes a different relationship from a BMS alarm point. A carrier circuit number and a tenant alias can both be valid while referring to different parts of the same handoff.

Start by writing the precise question: which service does this segment carry, which equipment connection belongs to this hose, what does this alarm represent, where does this pathway continue, or who owns this demarcation? Retain the visible reference and each conflicting source separately until the relevant owner resolves their relationship.

This collection brings those facility references together. The shared task is accurate identification and ownership; each guide retains its own equipment and work-scope limits.

## Choose the guide for that boundary

| What is unclear? | Start here | The context that must stay with the name |
|---|---|---|
| A pipe marker's service, supply/return role, or direction | [Cooling-pipe identification](https://datacenterlabeling.com/problems/cooling-pipe-identification) | Identified system, fluid, segment, controlling drawing, and documented direction. |
| A replaceable hose's two connections | [Liquid-cooling hose endpoints](https://datacenterlabeling.com/problems/liquid-cooling-hose-endpoints) | Hose identity, exact installed equipment names, model, and connection diagram. |
| A BMS name that does not match a physical unit | [Facility equipment-name crosswalk](https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk) | Monitoring-system scope, point reference, physical subject, drawing relationship, and owners. |
| A tray or pathway that cannot be followed in the drawing | [Pathway and route identification](https://datacenterlabeling.com/problems/pathway-route-identification) | Bounded segment, location, drawing revision, and adjacent segments. |
| Carrier, colo, and tenant circuit references that differ | [Colocation demarcation](https://datacenterlabeling.com/problems/colocation-demarcation) | Provider IDs, A/Z endpoints, responsibility boundary, and any onward tenant patch. |

A repeated short hose or equipment name usually needs more context before it needs a replacement. A BMS point may describe a sensor, group, or calculated condition rather than one physical asset. Likewise, do not resolve a pipe-direction disagreement by borrowing the color meaning of a nearby system.

## Close the relationship and retain its limits

Completed evidence should let another reviewer locate the exact segment, connection, equipment subject, or handoff. Keep the accepted relationship, controlling reference and revision, responsible owner, original conflicting values, and closure evidence together. Preserve unresolved portions rather than labeling an entire system accepted because one segment was checked.

For hoses and pipes, identification review does not authorize connecting, disconnecting, or changing the system. Manufacturer-specific color and routing information remains specific to the installed equipment. For pathways, a route label does not establish the condition of a penetration or its firestopping. For colocation, a crosswalk does not order or authorize a service change.

These limits are part of a useful handoff: they tell the next team what was established and which decision still belongs elsewhere.

## Resolve dependencies without expanding the task

If a facility asset has competing permanent and location names, use [asset versus location](https://datacenterlabeling.com/problems/asset-versus-location). If two systems keep restoring different values after correction, use [record reconciliation](https://datacenterlabeling.com/problems/label-record-reconciliation) to identify the field owner and update path. If a tray record points toward an uncertain termination, continue with [cable endpoint identification](https://datacenterlabeling.com/problems/cable-endpoint-identification).

The [requirements planner](https://datacenterlabeling.com/guides/labeling-standards-and-project-requirements) helps separate local administration from equipment, safety, and material requirements. The [legacy-room planner](https://datacenterlabeling.com/guides/legacy-room-relabeling) helps sequence a larger cleanup around the actual facilities, electrical, records, and provider dependencies instead of treating every label as one undifferentiated print job.