Rackstamp, data center labeling field guide

WORKSHEET 32 / Cooling & facilities

Cooling loop and unit service register

Name the facility and technology loops separately, then record which unit serves which racks against the schematic.

Download workbook ↓Read the guide

The download includes all 32 worksheets. Open the 32 Cooling loops tab.

Use it with your own records.

  1. Download the workbook and open 32 Cooling loops.
  2. Enter your site and room scope and the project or policy reference.
  3. Use the blank amber table for actual records. The fictional example below it is a reference.
  4. Insert table rows when needed. Keep identifiers as text, including leading zeros.
  5. Follow guide 32 to complete the checks and record unresolved items.

Before you start

  1. Define the included units and the full location scope, separating the loop as a named circuit from the unit that serves it and the racks it reaches.
  2. Collect the mechanical schematic and its revision, the distribution unit asset records, the monitoring configuration, and any deployment package affecting the served sets.
  3. Confirm how local policy distinguishes a controlled loop reference, a monitoring display name, and a unit asset identity.
  4. Establish whether each served set will be taken from the schematic, from observation, or from both, and record that basis before completing rows.

Complete the register

  1. Enter the Unit ID as the controlled asset identity, keeping any monitoring alias and observed label text in their own fields.
  2. Record the facility-side and technology-side loop references separately, preserving a shared colloquial name as an alias rather than a controlled value.
  3. Enter Serves as a list of rack, manifold, or enclosure identities, and record whether the set is complete against the schematic.
  4. Record Set basis explicitly so a set confirmed only by walking the aisle is distinguishable from one checked against the drawing.
  5. Record Redundancy only where a document establishes it, naming that reference and stating whether the arrangement is concurrent or standby.
  6. Preserve conflicting claims from different source systems with their sources instead of choosing a winner in the worksheet.
  7. Attach evidence for each row and link the owner decision and any monitoring change reference raised by the review.

Walk through the example

For the fictional LCASE-G32-301 survey in DC01 / H1, record the rack label text naming TCS-G32-002, the asset record for CDU-G32-301, and the monitoring alias shown against CDU-G32-302 as separate values, with schematic MECH-G32-340 revision 4 cited for all of them. The first finding is an alias collision, not a duplicated loop. DEC-G32-002 establishes that TCS-G32-002 is served by CDU-G32-301 and that CDU-G32-302 serves TCS-G32-003, whose display name was configured during commissioning and never corrected. Keep both controlled loop references, record the alias against CDU-G32-302 as a known display discrepancy, and raise the correction with the monitoring owner rather than relabelling racks. Link EV-G32-311 and review the rack labels in both rows, listing the four found carrying the display name. Record the actual review date. The completed row explains which assignment was reconciled to which revision; it does not assert capacity or establish a failover relationship.

Handle common exceptions

One rack appears under two different units.

Keep both claims with their source systems and refer the conflict to the mechanical owner. Deleting the less likely claim removes the evidence that a reconciliation was needed.

A secondary loop is shared across several units with no single owner.

Record the served set at the loop level and each unit’s contribution as its own relationship, rather than duplicating the full rack list under every unit.

A unit was replaced while the loop and served set stayed the same.

Keep the loop reference stable and record the unit change as its own history entry with an effective reference, including the new asset identity, model, and alias.

Review and close

  1. Confirm no single name is used on both sides of the heat exchanger and that both loop references are controlled values.
  2. Check that every served set lists identities and carries its basis, and that sets were compared against the recorded schematic revision.
  3. Keep unit-replacement history retrievable so behaviour in an earlier period is not attributed to a later unit.
  4. Review the racks in an affected row for labels carrying a monitoring display name rather than the controlled reference, and list them for correction.
  5. Record the actual verification date and retain unresolved redundancy or capacity questions separately from any commissioning acceptance.

Fields and filled example

Fictional values only. Scope: DC01 / H1 unless another location is shown. The downloadable register is blank for your actual observations.

FieldWhat to recordFictional example
Unit IDControlled asset identity of the distribution unit.CDU-01
Observed labelUnit label text preserved exactly as observed.LOOP 2
Monitoring aliasDisplay name in the monitoring system, kept separate.Loop 2
Facility loopFacility-side loop reference serving the unit.FWS-01
Technology loopTechnology-side loop reference distributed by the unit.TCS-02
ServesRacks, manifolds, or enclosures in the served set.RCK-401 .. RCK-408
Set basisWhether the set came from the schematic, observation, or both.Schematic and observation
RedundancyDocumented arrangement and the reference establishing it.Not established in records
SchematicControlling schematic and revision.Example MECH-340 rev 4
StatusIdentity-review state or unresolved detail.Alias collision pending review
EvidenceObservation and record references supporting the row.Fictional EX-32; schematic r4
OwnerTeam responsible for the mechanical system.Example mechanical owner
Verification dateActual date the assignment is reviewed.Not verified (fictional)
32 Cooling loops workbook preview
32 Cooling loops workbook preview. View full size ↗

Sources and scope