Data Center Operations
Data Center Operations is the FactVerse module for facility and equipment operations in data centers. It brings asset identity, data-hall context, BMS point mapping, equipment health, predictive maintenance, alert diagnosis, work-order dispatch, SLA review, and closed-loop evidence into one operating workflow.
Use this guide when a data center operations team needs to connect source-system records with a governed digital twin, review current operating risk, and prepare maintenance actions with traceable evidence.
For AI-assisted analysis surfaces, see Data Center Operations AI Tools.
Current service boundary
Data Center Operations is implemented across several runtime surfaces:
| Surface | Current role |
|---|---|
| FactVerse frontend | Provides data center overview, data hall filtering, asset list and detail, predictive queue, diagnosis console, closed-loop view, operations dashboard, BMS mapping view, and model-ops status. |
| Core backend and Data Center Operations services | Provide /api/v1/dcops dashboards, KPIs, asset reads, health trends, prediction history, diagnosis history, planning recommendations, dispatch candidates, closed-loop records, BMS mappings, operations analytics, snapshot export, and live event stream. |
| Inspector and work orders | Provide alert, work-order, feedback, attachment, and field execution context for operating actions. |
| Predictive Maintenance | Provides the broader equipment health and remaining-life workflow when data center assets need detailed maintenance analysis. |
| DFS | Prepares source data, BMS mappings, meter readings, work records, equipment identity, and governed datasets before operations depend on them. |
| AI Engine and Advisor | Provide health scoring, remaining-life estimation, alert diagnosis text, and optional standard or NVIDIA-backed execution metadata where enabled by the project. |
The module supports operational review and maintenance workflow preparation. Site teams should confirm data mappings, engineering assumptions, and action approval before using outputs for field execution.
Operations workflow flow
What users can do today
| Workflow | What users can review or perform |
|---|---|
| Overview dashboard | Review asset counts, alert state, work-order state, data hall scope, health score, PUE and WUE indicators when data is mapped, and operating risk signals. |
| Asset operations | Review data center assets, equipment detail, recent alerts, latest diagnosis, open work orders, health trend, prediction history, and remaining-life intervals. |
| Health review | Calculate or read equipment health scores, risk levels, anomaly scores, and aggregate health distribution. |
| Predictive queue | Review 7, 30, and 90 day risk buckets, high-risk equipment, remaining useful life intervals, and maintenance attention candidates. |
| Diagnosis console | Create or read alert diagnosis records, review confidence, trace ID, evidence source, and diagnosis history. |
| Dispatch and closed loop | Review pending dispatch candidates, approve work-order creation, link feedback, and inspect whether diagnosis, action, and feedback evidence are complete. |
| Planning | Review maintenance planning recommendations, generate draft plans, inspect conflicts, and resolve time-window or resource conflicts. |
| Operations dashboard | Review queue aging, SLA rates, SLA breach list, diagnosis reuse, dispatch conversion funnel, KPI deltas, trends, and exportable operations snapshots. |
| Live operations stream | Subscribe to operations events for alerts, work orders, and risk snapshot updates. |
| BMS mapping | Review, validate, and publish source-point to target-field mapping rules for BMS data. |
| Model operations | Review the active engine mode, fallback metadata, and status indicators for standard or NVIDIA-backed execution paths. |
Before you start
Prepare the tenant, site, and source data needed for the workflow:
| Requirement | Notes |
|---|---|
| Tenant and site context | DCOps reads are tenant-scoped. Site and data center filters should match the active operating scope. |
| Permissions | Main read surfaces use dcops.view. Prediction surfaces use dcops.predict.view. Diagnosis and work-order actions require the matching diagnosis, work-order, or feedback permissions. |
| Asset identity | Equipment records should have stable equipment IDs, names, type, location, criticality, and data hall or room assignment. |
| Source mappings | BMS points, alerts, work orders, meter readings, and equipment records should map to the same asset identity. |
| Work ownership | Define who reviews alerts, accepts dispatch candidates, assigns work orders, resolves SLA breaches, and records feedback. |
| Data quality | Confirm timestamps, units, source freshness, missing values, and stale mappings before interpreting health or prediction output. |
| Review record | Keep diagnosis text, trace IDs, work-order links, feedback, and snapshot exports with the operating review. |
For source data setup, start with Getting Started with DFS, Connect BMS to a Facility Twin, and Prepare Predictive Maintenance Signal History.
Open Data Center Operations
Open the FactVerse application and use the Data Center Operations workspace. Current frontend surfaces include:
| View | Route |
|---|---|
| Overview | /datacenterops/dashboard |
| Asset list | /datacenterops/assets |
| Asset detail | /datacenterops/assets/:assetId |
| Predictive queue | /datacenterops/predictive-queue |
| Diagnosis console | /datacenterops/diagnosis |
| Closed-loop view | /datacenterops/closed-loop |
| Operations dashboard | /datacenterops/operations |
| Integrations | /datacenterops/integrations |
Module availability depends on tenant configuration. The backend guard uses the Data Center Operations module enablement setting before serving /api/v1/dcops paths.
Prepare operational data
Data Center Operations depends on a consistent operating data package:
| Data area | Typical preparation |
|---|---|
| Asset hierarchy | Map sites, data centers, data halls, rooms, racks, equipment, and criticality to stable IDs. |
| BMS points | Map source point names to target fields and validate rule coverage before publishing. |
| Alerts | Map alert severity, status, title, source equipment, and timestamps to the asset layer. |
| Work orders | Connect open, assigned, in-progress, completed, and feedback records to alerts and equipment. |
| Meter and energy readings | Prepare power, water, or other utility readings with units and time windows for operating review. |
| Predictive signals | Prepare health snapshots, failure prediction history, and remaining-life inputs for maintained assets. |
Use DFS when source systems need connector configuration, source-to-target mapping, sync monitoring, data-quality review, and governed dataset preparation.
Review dashboard and assets
Start from the overview dashboard, then drill into assets:
- Select the relevant site or data center scope.
- Review asset, alert, work-order, health, and risk summary cards.
- Open the asset list and filter by risk or equipment type.
- Open an asset detail page to review recent alerts, diagnosis records, open work orders, health trend, prediction history, and feedback status.
- Export or save the operating snapshot when the review needs to be shared.
PUE and WUE indicators should be read as operating review signals. Confirm meter coverage, load definitions, and calculation assumptions before using them in management reporting.
Review health and predictive risk
The module can calculate or read equipment health and predictive risk:
| Area | What to check |
|---|---|
| Health score | Composite score, risk level, anomaly score, engine mode, timestamp, and factor breakdown when available. |
| Health trend | Recent health-score history for the selected asset and review window. |
| Prediction history | 7, 30, and 90 day failure probabilities, remaining-life range, model version, and engine mode. |
| High-risk equipment | Equipment whose predicted risk passes the selected threshold and time window. |
| Predictive queue | Risk buckets for near-term maintenance planning and operations meetings. |
Treat health and prediction output as evidence for review. Maintenance owners should compare the output with inspections, work orders, source signal freshness, and site constraints before approving action.
Diagnose alerts and close the loop
The diagnosis workflow connects alerts to work orders and feedback:
- Open the diagnosis console or an alert detail.
- Review the alert severity, affected equipment, recent alert pattern, and source timestamps.
- Create or read a diagnosis record.
- Check confidence, trace ID, evidence source, and diagnosis history.
- Create or link a work order after an owner accepts the recommended action.
- Record feedback when the work order closes.
- Confirm the closed-loop view includes diagnosis, action, and feedback evidence.
Diagnosis may use Advisor-backed text generation or a rule-based fallback. Both paths should remain visible in the review evidence through source, confidence, trace ID, and audit record.
Plan and dispatch maintenance
Planning and dispatch views help teams turn risk into scheduled work:
| Surface | Use |
|---|---|
| Planning recommendations | Review candidate maintenance windows, estimated duration, priority, and risk score. |
| Planning draft | Generate a draft plan for a selected window and inspect resource or time-window conflicts. |
| Pending dispatch | Review open alerts that have no open work order yet. |
| Batch approve | Approve selected dispatch candidates after diagnosis reuse or diagnosis creation has been reviewed. |
| Bulk operator actions | Assign owners, normalize priority, append escalation notes, retry diagnosis, or reconcile closed-loop evidence when permissions allow it. |
Keep action ownership clear. Bulk operations should be used for triage and queue management after the shift lead or operations owner approves the selected records.
Review BMS mapping and model operations
BMS mapping defines how source data becomes useful operational context:
- Open Integrations.
- Review the latest published BMS mapping version and source.
- Validate mapping rules for required
sourcePointandtargetFieldcoverage. - Publish mapping changes after source owners confirm the mapping.
- Keep the audit record with the operating handover.
Model operations exposes engine mode and status metadata. Use it to confirm whether the workflow is running in the standard path or a project-enabled NVIDIA path, and record fallback or degraded status during acceptance.
API surface
Data Center Operations APIs are grouped under /api/v1/dcops:
| Group | Example endpoints |
|---|---|
| Overview and KPIs | /, /dashboard/overview, /dashboard/overview/trends, /dashboard/kpis |
| Assets and health | /assets, /assets/rul-intervals, /assets/{assetId}/detail, /assets/{assetId}/health, /assets/{assetId}/health/trend, /health/summary |
| Predictions | /assets/{assetId}/predictions, /assets/{assetId}/predictions/history, /predictions/high-risk |
| Diagnosis | /diagnosis/from-alert/{alertId}, /alerts/{alertId}/diagnosis, /alerts/{alertId}/closed-loop |
| Planning | /planning/recommendations, /planning/generate, /planning/{planId}/conflicts, /planning/{planId}/resolve |
| Dispatch and feedback | /dispatch/pending, /dispatch/alerts/{alertId}/approve, /dispatch/batch-approve, /recommendations/{diagnosisId}/create-work-order, /work-orders/{workOrderId}/feedback, /work-orders/{workOrderId}/closed-loop |
| Operations dashboard | /dashboard/operations, /dashboard/operations/kpi-delta, /dashboard/operations/queue-aging, /dashboard/operations/predictive-queue, /dashboard/operations/trends, /dashboard/operations/sla-rates, /dashboard/operations/sla-breaches, /dashboard/operations/diagnosis-reuse, /dashboard/operations/dispatch-funnel, /dashboard/operations/snapshot, /dashboard/operations/snapshot.csv, /dashboard/operations/events |
| Integrations and model ops | /integrations/bms/mappings, /integrations/bms/mappings/validate, /integrations/bms/mappings/publish, /model-ops/status, /model-ops/engine-mode |
| Automation helpers | /automation/diagnosis/bulk-retry, /automation/close-loop/reconcile, /dashboard/operations/risk-chips/bulk-assign-assignee, /dashboard/operations/risk-chips/bulk-normalize-priority, /dashboard/operations/risk-chips/bulk-sla-escalation-note |
Validation checklist
Before using Data Center Operations output in an operations meeting or maintenance decision, confirm:
- tenant, site, and data center filters match the review scope;
- asset, equipment, alert, BMS point, meter, and work-order IDs resolve to the same operating objects;
- source timestamps, units, and freshness are acceptable for the decision;
- BMS mapping changes have owner approval and audit evidence;
- health and prediction outputs are reviewed with inspection and work-order context;
- diagnosis records include trace ID, evidence source, confidence, and responsible reviewer;
- work-order feedback is recorded after action so the closed-loop view can reflect the outcome;
- exported snapshots and CSV files are stored with the operating review package when used in handover.