EPMS Telemetry Cockpit
Single-line electrical telemetry, source/bus/breaker state, demand, power quality, alarms and deterministic operating interactions.
Electrical telemetry · source-tag binding
Home / Product Requirements
Deterministic product contracts
Telemetry Cockpit Product Requirements
Six public, implementation-traceable contracts for ResistanceZero electrical, cooling and data-hall cockpits. Each PRD fixes scope, functions, telemetry provenance, formulas, acceptance evidence and known limitations; each pairs with a deeper engineering manual.
AI / HPC Data Hall
GB200 racks, CDU operation, direct-liquid cooling, electrical balance, alarms and basis-of-design traceability.
Restricted cockpit · public documentation
Conventional Data Center
EPMS/BMS operating states, 2N electrical topology, PUE/WUE/CUE, capacity and alarm reconciliation.
Restricted cockpit · public documentation
Data Hall SCADA Console
Deterministic rack distribution, CRAH capacity, cold-aisle state, cooling margin and alarm thresholds.
1,850 kW IT · 200 rack cells
CDU Mini-BMS
Five liquid-cooling architectures, thirteen instrument points, coherent fault scenarios, trends and guided response.
5 types · 13 signals · 6 scenarios
RZ Cockpit Re-skin Mockup
Honest before/after visual prototype for industrial-register styling with semantic colors preserved and gaps declared.
Seeded fixture · visual authority only
How to use these contracts. Start with scope and non-goals, follow each telemetry point to its source binding, reproduce the formulas in the paired Manual, then evaluate the AC matrix. A public document does not remove an access gate from a restricted cockpit, and a simulated value is never evidence of a live facility condition.