# Facility equipment and alarm-name crosswalk

> Link BMS alarm names and point references to physical equipment, location, model, drawings, and evidence in the editable crosswalk.

Canonical page: https://datacenterlabeling.com/templates/facility-equipment-name-crosswalk

Download: https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx

Workbook tab: 18 Equipment aliases. The workbook includes all 30 registers.

Rackstamp provides editorial field guidance. IDs, cases, and worksheet entries are fictional examples unless identified otherwise. Distinguish local conventions from adopted standards. Source notes describe the evidence scope; a linked overview is not the full standard or a project approval.

## 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 fictional filled example

| Field | What to record | Fictional example |
| --- | --- | --- |
| Equipment ID | Canonical physical unit identity. | CDU-003 |
| BMS scope | System instance or alias namespace. | WEST-BMS |
| Alarm/BMS name | Exact displayed or exported alias. | H1.Cooling03.Fault |
| Point reference | Stable source-system point key, if available. | Example PT-443 |
| Subject type | Unit, sensor, or documented group. | Unit |
| Location | Physical location of the linked subject. | DC01-H1-CDU bay |
| Model | Supporting equipment model reference. | Fictional HX-300 |
| Drawing | Equipment schedule or drawing and revision. | Example M-10 rev 4 |
| Status | Mapping-review status or conflict. | Pending crosswalk review |
| Evidence | BMS export and physical-record references. | Fictional export EX-18; asset register r3 |
| Owner | Accountable facilities/controls record owner. | Example controls records owner |
| Verification date | Actual date the alias relationship is checked. | Not verified (fictional) |

## Sources

- [ServiceNow: Identification and reconciliation configuration](https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/configuring-ire.html?contentId=Qy3dDh~jSw5JICJGU2x7zg): Identification and update-authority concepts. The BMS crosswalk is this library's editorial workflow.
- [Vertiv: Liebert XD system design manual](https://www.vertiv.com/49f56b/globalassets/shared/liebert-xd-system-design-manual_00.pdf): Liebert XD system design manual SL-16655_REV17_08-24, §3.11, printed pages 24–25 (PDF pages 30–31). Equipment-specific supply/return context; does not prescribe a BMS crosswalk.
- [Lenovo: N1380 manifold instructions](https://pubs.lenovo.com/n1380/install_the_manifold): Manufacturer-specific identification context only. All zone, point, hose, system, and ownership relationships here are fictional editorial examples; no universal coupling boundary or alarm-response instruction.