Data center operations · AI copilots

Run the floor with an agent that already read every runbook.

Plenum pairs your NOC with Claude-powered agents that triage alarms, plan capacity, and keep PUE honest — grounded in your real telemetry, not guesswork.

N+1 aware MCP native SOC 2 path Human-in-loop by default
SITE SG1 · HALL B
PUE (rolling)
1.31
▼ 0.04 vs 7d
IT Load
4.82 MW
68% of design
Cold-aisle temp · Row 04–11
22.4°C within ASHRAE A1
CLAUDE Correlated 3 alarms → CRAC-7 fan degradation. Drafted runbook DR-114. 09:41
AUTO Failover verified on PDU-2B, load rebalanced. 09:38
WATCH Humidity drift Hall B trending to 62% RH. 09:33
What Plenum does

Six jobs on the operations floor, handled with judgment.

Each capability is an agent grounded in your DCIM, BMS, and ticketing data through the Model Context Protocol — so answers cite the reading, the rack, and the runbook.

Incident triage & correlation

Collapses alarm storms into a single root cause, ranks blast radius against N+1 headroom, and drafts the response before you finish reading the page.

MTTR ↓ · alarm noise ↓

Capacity & power planning

Models rack-level kW, stranded capacity, and breaker margins so the next deployment lands where power, cooling, and space actually agree.

stranded capacity ↓

Energy & PUE optimization

Watches PUE, WUE, and setpoints in context, flags free-cooling opportunities, and explains the trade before anyone touches a setpoint.

PUE trend · kWh saved

Runbook copilot

Turns tribal knowledge into living runbooks, walks an on-call engineer through MOPs step by step, and logs every action back to the ticket.

on-call assist · audit trail

Shift handover

Compiles the last 12 hours into a signed handover — open incidents, deferred work, and what to watch — in the language your team already uses.

handover in seconds

Change & compliance

Pre-flights every MOP against dependencies and freeze windows, and keeps an evidence trail auditors can read without a translator.

change risk ↓ · evidence ready
Live demo · powered by Claude

Paste an alarm burst. Watch it collapse to one root cause.

This isn't a mockup — it calls Claude on our server to correlate the alarms below. Edit them, or load a scenario, then run the triage.

ALARM INGEST · paste or edit
Verifying you’re human…
CLAUDE · triage output
▷ Run the triage to see Claude correlate these alarms into a root cause, blast radius, and next actions.
The Claude layer

An agent that reasons over your floor — with a human on every irreversible action.

Claude connects to your systems through MCP servers you control. It reads, reasons, and recommends; people approve anything that moves power, load, or cooling.

01 · CONNECT

Ground in real telemetry

MCP servers expose DCIM, BMS/SCADA, and ITSM read-only. No data leaves your boundary without a policy.

02 · REASON

Correlate & explain

Claude links alarms, telemetry, and history into one narrative — with the readings it used shown inline.

03 · PROPOSE

Draft the action

It writes the runbook step, the ticket, or the capacity plan — scoped, reversible, and ready to review.

04 · APPROVE

Human in the loop

An engineer signs off. Only then does anything execute, and every step lands in the audit log.

Illustrative targets

What good looks like after 90 days.

Directional figures from comparable AIOps rollouts — your baseline sets the real numbers.

41%
Lower mean time to resolve
6.2×
Alarm-to-signal reduction
0.05Δ
PUE improvement, rolling
99.98%
Uptime SLA held
Proof of concept

Point Plenum at one hall. See it correlate a real alarm.

A two-week pilot on read-only data — no changes to your control systems.