Rackstamp, data center labeling field guide

WORKSHEET 18 / Cooling & facilities

Facility equipment and alarm-name crosswalk

Link the name seen in an alarm to the physical equipment, drawing, and controlled asset record.

Download workbook ↓Read the guide

The download includes all 30 worksheets. Open the 18 Equipment aliases tab.

Use it with your own records.

  1. Download the workbook and open 18 Equipment aliases.
  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 18 to complete the checks and record unresolved items.

Before you start

  1. Define the included alias or point population and capture the authorized BMS source, system scope, export date, and available stable point keys.
  2. Collect the physical asset register, location plan, equipment schedule or drawing, and replacement or rename history relevant to those aliases.
  3. Identify facilities and controls owners separately, including who can accept a relationship and who can update each source system.
  4. Prepare to distinguish units, sensors, points, and documented groups rather than forcing every alias into a single-equipment interpretation.

Complete the register

  1. Copy BMS scope and Alarm/BMS name exactly, preserving suffixes, punctuation, and the source-system Point reference where available.
  2. Determine the Subject type through the controls record and keep unresolved subject meaning visible for its owner.
  3. Enter the canonical Equipment ID for a physical unit relationship and retain any narrower sensor or broader group reference needed to describe the subject accurately.
  4. Record Location and Model as supporting context and link the Drawing or equipment schedule revision used in the match.
  5. Preserve current and historical aliases, competing asset associations, and their effective events rather than deleting inconvenient duplicates.
  6. Record the owner-accepted crosswalk and supporting evidence, then check lookup from alias to subject and from subject to the included aliases.
  7. Leave proposed BMS display or binding changes separate from the worksheet's reviewed identity relationship and its completion state.

Walk through the example

For H1.COOLING.BAY3.FAULT in BMS-G18-301, enter the exact display name and PT-G18-301 before attempting to match the physical unit. Preserve CDU-G18-301 from the old crosswalk and link the observation showing CDU-G18-302 in DC01 / H1 / cooling bay C3. Cite CH-G18-301 as the replacement context and mark the relationship pending owner review. DEC-G18-301 establishes that the scoped fault point now refers to the replacement unit. Enter subject type Unit and the current asset relationship, while retaining the old association with its end event. Check that the alias lookup reaches CDU-G18-302 and that the asset lookup returns the included point. Link physical evidence and the controls association separately, record the actual review date, and retain the historical alias relationship. The row confirms navigation and identity for this point; it does not validate every alarm or authorize a BMS change. Keep the unchanged operating alias distinct from the new unit's durable identity in every lookup view.

Handle common exceptions

The alias is a group alarm rather than one unit.

Record a documented group subject and membership reference, and avoid placing an arbitrary member in the equipment field as if it were the whole subject.

A physical replacement retained the same operating name.

Review the replacement event, establish the new current asset relationship, and retain the former subject and effective history.

The source display omits a point suffix or stable key.

Preserve the visible name as observed and obtain the accepted full source reference before merging or approving apparently duplicate alias rows.

Review and close

  1. Confirm the exact alias resolves within the stated BMS scope to the accepted subject type and relationship.
  2. Verify the physical asset evidence where applicable and the separate controls reference supporting the point association.
  3. Check reverse lookup from the current asset or subject and retain relevant historical relationships for replacements or renames.
  4. Keep unreviewed points, unresolved group membership, and missing stable keys explicitly bounded rather than marking the entire alarm system verified.
  5. Record the actual crosswalk-review date and distinguish identity completion from controls changes or functional alarm testing.

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
Equipment IDCanonical physical unit identity.CDU-003
BMS scopeSystem instance or alias namespace.WEST-BMS
Alarm/BMS nameExact displayed or exported alias.H1.Cooling03.Fault
Point referenceStable source-system point key, if available.Example PT-443
Subject typeUnit, sensor, or documented group.Unit
LocationPhysical location of the linked subject.DC01-H1-CDU bay
ModelSupporting equipment model reference.Fictional HX-300
DrawingEquipment schedule or drawing and revision.Example M-10 rev 4
StatusMapping-review status or conflict.Pending crosswalk review
EvidenceBMS export and physical-record references.Fictional export EX-18; asset register r3
OwnerAccountable facilities/controls record owner.Example controls records owner
Verification dateActual date the alias relationship is checked.Not verified (fictional)
18 Equipment aliases workbook preview
18 Equipment aliases workbook preview. View full size ↗

Sources and scope