Scenario 04

The Campus Layer

Four buildings. One campus. One operating intelligence layer. Each building is managed by its own BMS, SCADA, and DCIM. Synestra observes them all together — and sees what no individual building system can see.

Scenario: Illustrative hyperscale campus, four buildings. Synthetic data.

Each building has its own operations team, its own systems, and its own view of its own performance. What they cannot see is how a decision in Building 1 affects the economics of Building 3 — because no single building system observes both.

Building 01

West Campus — Phase 1

Critical IT load320 MW

EA score94.2%

Active consequences0

Cross-campus signal↑ Chilled water return temp elevated

Building 02 · Consequence active

West Campus — Phase 2

Critical IT load280 MW

EA score88.7%

Active consequences1 — cooling oscillation, Hall B

AdvisoryIssued — pending operator action

Building 03

East Campus — Phase 1

Critical IT load350 MW

EA score96.1%

Active consequences0

Cross-campus signalNo shared-plant signals

Building 04

East Campus — Phase 2

Critical IT load190 MW

EA score91.4%

Active consequences1 — workload placement opportunity

AdvisoryPending — cross-building analysis

Campus Operating Layer · Synestra

Total campus EA score 92.6% (target: 97%)

Recoverable value — current gap Modeled — see EA report

Active cross-building signals 1 — B01 chilled water return affecting B02 oscillation

Consequence patterns validated (90 days) 47

Recurrence detected before threshold alert 83% of validated patterns

Campus operational memory age Day 94

The cross-building insight this illustrates

Building 1's chilled water return temperature — normal within Building 1's own BMS thresholds — is contributing to the cooling oscillation in Building 2. Building 1's operations team is unaware. Building 2's operations team sees the oscillation but not the upstream cause. Synestra observes both buildings simultaneously and traces the causal chain across the campus boundary. No individual building system can do this, because no individual building system observes both buildings.

Why this view matters at hyperscale

At 1 GW of critical IT capacity across four buildings, a 4% EA gap — the difference between 92.6% and 96.6% — represents a significant economic consequence every year. That gap cannot be closed building by building, because much of it lives in the interactions between buildings. Synestra is designed to operate at campus scale — not as four separate deployments, but as one intelligence layer observing the entire operating environment.

These are illustrative workflows

Every figure in this scenario is synthetic. The EA scores, building loads, consequence counts, and pattern library numbers are representative of the intended experience — not measurements from a production deployment. The operational logic they demonstrate, however, is the actual design intent of the Synestra platform.

See how a real pilot works Back to all scenarios