Asset and BMS Context

Use this guide when the operations team needs to connect data center assets, data-hall locations, BMS points, meter readings, alerts, and work records into one operating context.

Context Flow

Prerequisites

Requirement	Why it matters
Data-hall hierarchy	Operators need site, room, zone, rack area, and equipment relationships.
Stable equipment ID	BMS points, alerts, and work orders need the same asset reference.
Mapping owner	Source point meaning and unit conversion require engineering review.
Criticality model	Priority and SLA review depend on equipment role and affected service.

Inputs

Input	Required preparation
Asset record	ID, name, type, location, criticality, owner, manufacturer, and model.
BMS point	Source name, target field, unit, scale, source equipment, and timestamp.
Meter relationship	Meter, equipment, room, utility type, and aggregation rule.
Alert relationship	Alert source, severity, affected asset, status, and event time.
Work relationship	Open work, recent completed work, feedback, and closure evidence.

Procedure

1. Build the site, data hall, room, and equipment hierarchy.
2. Map each monitored equipment record to source-system aliases.
3. Validate BMS point mappings for required fields, units, and scale.
4. Connect meter readings to the asset, room, or service boundary they represent.
5. Confirm alerts resolve to the same asset record used by work orders.
6. Record the mapping version, reviewer, and approval date.

Expected Output

The result is a reviewed asset context that lets dashboards, diagnosis, dispatch, energy review, and SLA reporting point to the same equipment object.

Validation Checklist

• Each critical asset has one stable operating identity.
• BMS points have target fields, units, timestamps, and mapping status.
• Meter relationships show whether values belong to equipment, room, hall, or site scope.
• Alerts and work orders can be opened from asset detail.
• Mapping changes keep an audit trail.

Failure Handling

Symptom	Response
One equipment appears under several names	Create an alias review and keep only one operating asset ID.
BMS unit is unclear	Hold the mapping in review until engineering confirms the unit and scale.
Meter scope is ambiguous	Mark the reading as site, hall, room, or equipment level before using it in summaries.
Alerts do not resolve to assets	Fix source equipment mapping before using diagnosis or dispatch views.

Related Docs

• Data Center Operations
• Operational Data Readiness
• Connect BMS to a Facility Twin