Research — Auto Demo · Precomputed (draft, unvalidated)

Generation to rack: power path N-1 — auto

No controls here: five short stories play on their own. Losing a lineup loses exactly one rack row. A 2+1 chiller plant survives one loss and not two. A pump plant with no standby is already tight until a standby is added. A fixed transformer is outgrown by heavier racks until the harness picks the next size. A loop leg loses nothing, the source loses everything. Use Pause, or the story and step buttons, to stop on any frame.

Story

Datacenter hall · generation to rack, isometric

energizedno powerfailedpast a limit the data namesstandby now runningidle standby

One-line diagram · the same hall, click any symbol or run

Source and MV loop at the top, one padmount transformer and LV lineup per rack row, each lineup feeding its rack row, its CDUs and the chillers and pumps assigned to it. Bars: loading, % of that transformer's nameplate (dashed ticks: the design limit the data states and 100 %).

Every check at this step · the controlling row is highlighted

Rule column: the citation the data file gives for each check.

How the checks read it

Every check · before the event, the event, the fix

Required values are read from the data file. Tight is the harness's warn (partial capacity), not a failure.

Precomputed results:every verdict, required value and margin on this page was computed by the real Python harness at export time and is played back from a data file. The page runs no harness logic and holds no standards tables, and it never interpolates between exported values. Not a live API call. Precomputed by the real functions build_generic_hall, build_load_schedule, build_one_line and pick_transformer_kva in datacenter-power-harness (recorded commit da85dad; exported from the working tree on top of it), a v0.1 draft, unvalidated. Every kW, count and rating shown is a round illustrative placeholder. Steps tagged harness are the harness's own results. The harness has no per-element failure function, so steps tagged demo logic come from this demo's own counting over the harness one-line, and the ring layout and the "no backup source" assumption are demo logic. Cooling equipment is a placeholder not scaled to the IT load. No catalog or product data is used. Domain maturity: starting inventory, not a completed review.Real functions this maps to:build_generic_hall, build_load_schedule, build_one_line, pick_transformer_kva.Not modeled: backup generation or batteries, protection and relay coordination, cable ampacity and fault withstand, a real cooling load model, CDU-level redundancy, transformer re-sizing after an event, and any real site layout. The drawing is schematic.See also:Power path N-1, interactive with free play · Cooling capacity margin, hands-off