Data center resilience analysis

Understand capacity through every modeled event.

Run a deterministic reference scenario, inspect the electrical-path state at each transition, and trace every result to its model version and input hashes.

Reference scenario

Select and run

Scenario

Scenario details will appear after the reference catalog loads.

Replay compares deterministic computation hashes for the same scenario.

Compare two scenarios

Scenario A

Scenario B

Both scenarios run sequentially and their outcomes appear side by side.

Loading scenario catalog

Connecting to the read-only simulation API.

No simulation result yet

Select a reference scenario and run it to inspect service, topology, and event evidence.

Simulation result

Scenario outcome

Demanded energy

—

Across this modeled scenario only

Why this value?

Served energy

—

Delivered by modeled available paths

Why this value?

Unserved energy

—

Demand not served in this scenario

Why this value?

Scenario service ratio

—

Not a site-availability or SLA claim

Why this value?

Modeled redundancy state

—

Scenario state, not certification

Why this value?

Deterministic replay

Timeline position

—

Select a timeline position to inspect modeled state.

Modeled capacity paths

Topology at selected time

— Unknown

The diagram reports modeled logical state and active-power capacity. It does not establish voltage, fault current, selectivity, or physical switching safety.

Selected interval

Served versus unserved load

Served — Unserved — Demanded —

Aggregate modeled UPS energy

—

Minimum: —

The value sums reported battery-energy states. It is synthetic and scenario-specific.

Causal evidence

Events and alarms

0 records

Ordered simulation transitions and alarms, including time, category, status, component, and explanation.
Time	Category	Status	Component	Explanation

Reproducibility

Run provenance

Run ID: —
Engine version: —
Computation hash: —
Snapshot hash: —
Scenario hash: —

Hashes identify modeled inputs and deterministic computation output. A matching hash supports reproducibility; it does not validate real-world equipment or operation.

Scenario comparison

Side-by-side outcome

Per-run metrics

Energy and service metrics

Scenario-level metrics for the two compared runs, one column per run.
Metric	Scenario A	Scenario B

Each column reports one deterministic run only. The values are scenario evidence, not availability or compliance claims.

Where the runs diverge

Timeline milestones

Merged UPS threshold, depletion, and restoration milestones with the modeled time in each run and whether the runs align.
Milestone	Scenario A	Scenario B	Alignment