Get Started with Data Center Operations
Use this guide when a team is preparing the first Data Center Operations workspace in FactVerse. The goal is to make asset identity, data-hall context, BMS points, alerts, work orders, energy readings, and review evidence usable in one governed operating workflow.
Setup Flow
Prerequisites
| Requirement | Why it matters |
|---|---|
| Site owner | Confirms which data center, hall, room, rack area, or equipment group is in scope. |
| Asset owner | Reviews equipment names, criticality, room assignment, and source-system aliases. |
| Data owner | Confirms BMS points, meters, alerts, work orders, and sync freshness. |
| Operations owner | Accepts dispatch candidates, reviews SLA risk, and approves field action. |
| Feedback path | Work-order results must return to the closed-loop operating record. |
Inputs
Prepare a small, trusted scope before rolling out broadly:
| Input | Preparation |
|---|---|
| Asset inventory | Site, data hall, room, rack zone, equipment ID, type, owner, and criticality. |
| BMS points | Source point, target field, unit, timestamp, mapping version, and review owner. |
| Alerts | Severity, status, source equipment, title, first seen time, and latest value. |
| Work orders | Open, assigned, in-progress, completed, feedback, owner, priority, and closure evidence. |
| Energy readings | Power, demand, water, or other meter values with units and time windows. |
Procedure
- Define the first operating boundary.
- Confirm that asset IDs match the equipment seen in BMS, alerts, and work orders.
- Validate the first BMS mapping version with source owners.
- Open the Data Center Operations dashboard and check summary cards.
- Open one representative asset and review alerts, diagnosis history, health trend, prediction history, and open work.
- Route one accepted diagnosis or dispatch candidate to a work order.
- Record feedback when work closes and confirm the closed-loop view reflects the outcome.
Expected Output
The first setup should produce a reviewed workspace with stable asset identity, mapped source data, active dashboard and asset views, a named operations owner, and one tested path from alert or predictive risk to work-order feedback.
Validation Checklist
- Site and data hall filters match the rollout scope.
- Asset, BMS, alert, meter, and work-order records resolve to the same operating object.
- Source timestamps, units, and freshness are visible.
- The dashboard and asset detail views show real source data or a clear no-data state.
- Work ownership and approval rules are visible before dispatch.
- Feedback appears in the closed-loop record after work closes.
Failure Handling
| Symptom | Response |
|---|---|
| Asset identity is inconsistent | Pause rollout and resolve aliases through the asset owner or DFS review. |
| BMS points do not map cleanly | Keep the mapping unpublished until source point meaning and unit are confirmed. |
| Dashboard values look stale | Check connector sync, source timezone, and latest reading timestamps. |
| Dispatch cannot be approved | Keep the recommendation as review evidence until owner, priority, and work path are confirmed. |