Design Pro Playbook
A systems atlas for comparing real data center design patterns without pretending that one answer fits every site.
The current release covers 33 real-world design patterns across 6 connected systems. It compares mechanisms and tradeoffs without producing a hidden composite score or a universal recommendation.
Energy & boundary
Define what is measured before comparing a ratio. Follow energy from the facility boundary to useful IT work.
PUE measurement boundary
Treat PUE as an energy ratio over a declared boundary and period—not a universal live efficiency score.
Mechanism: Divide total data center energy by IT equipment energy for the same period and a consistently defined boundary.
Power path
Trace dependencies from utility service through switching, conversion, distribution and the rack.
Utility-to-rack power path
Map every dependency between incoming service and the IT load before discussing redundancy.
Mechanism: Represent switchgear, conversion, storage, distribution and rack delivery as a connected path with explicit dependencies.
A/B rack feeds
Two rack feeds help only when the upstream paths and the load itself preserve the intended independence.
Mechanism: Feed dual-corded equipment from separately protected paths, or use an appropriate transfer strategy for single-corded loads.
Maintenance bypass
A bypass creates an alternate operating state so protected equipment can be isolated—but it also creates new hazards.
Mechanism: Provide a controlled route around a UPS or other maintainable element with interlocks, procedures and state indication.
Overhead busway distribution
A modular busway can simplify rack-feed changes, but fault duties, tap-off practices and overhead coordination still govern.
Mechanism: Distribute power along a rated bus with localized tap-off units instead of running a dedicated long cable to every rack.
Double-conversion UPS path
A double-conversion UPS continuously conditions the protected path, but its bypass, loading and loss behavior remain part of the design.
Mechanism: Convert incoming AC through a DC link and inverter while stored energy supports the inverter when the normal source is unavailable.
Modular UPS blocks
Modular power blocks can align capacity with load growth, provided the frame, controls and bypass are not mistaken for independent modules.
Mechanism: Add parallel conversion modules inside a coordinated UPS system so capacity or component redundancy can grow in smaller increments.
UPS energy-storage families
Battery and kinetic storage choices change autonomy, footprint, maintenance, environmental controls and failure response—not only runtime.
Mechanism: Store enough usable energy to bridge the protected load through the defined source-transfer or controlled-shutdown interval.
Standby generation
An engine-generator is a longer-duration alternate source whose real path includes start systems, fuel, cooling, controls, switching and testing.
Mechanism: Detect loss of normal power, start an alternate source, establish acceptable output and transfer eligible loads after the defined sequence.
ATS and STS transfer roles
Automatic and static transfer equipment serve different source and timing contexts; neither creates an independent source by itself.
Mechanism: Monitor acceptable sources and move an eligible load using the switching technology and sequence defined for that application.
RPP and cable distribution
Panel-and-cable distribution can provide familiar protection and routing, but physical pathway and change work grow with rack count.
Mechanism: Divide protected power at panels and route dedicated branch circuits through defined pathways to rack distribution units.
Thermal path
Follow heat from silicon to room air, liquid loops and final heat rejection while watching for mixing and stranded capacity.
Legacy open-room cooling
Room units and an open volume can support modest loads, but uncontrolled mixing and bypass air often hide the real constraint.
Mechanism: Supply conditioned air to the room and return mixed room air to perimeter or in-room cooling equipment.
Hot-aisle / cold-aisle layout
Alternating rack orientation creates coherent supply and return zones before physical containment is added.
Mechanism: Face rack inlets toward a common cold aisle and exhausts toward a common hot aisle.
Airflow hygiene
Blanking panels, sealed openings and deliberate tile placement can recover useful cooling before major plant work.
Mechanism: Close recirculation and bypass paths so conditioned air crosses IT equipment instead of escaping around it.
Aisle containment
A physical barrier reduces hot/cold mixing, but fire protection, egress, controls and failure behavior must be coordinated.
Mechanism: Contain either the supply or return air zone so rack inlet and exhaust streams remain separated.
Hybrid liquid-cooled zone
Liquid capture can remove part of the rack heat close to the source while a residual air system still serves the rest.
Mechanism: Split the heat path between a liquid loop and room air, then size controls, pumping and heat rejection for the actual split.
Network path
Trace packets through access, fabric, border and carrier dependencies while exposing cable and failure-domain consequences.
Diverse carrier entrances
Two carriers are not physically diverse when their routes converge in the same trench, building entrance, riser or room.
Mechanism: Trace each service from an external route through separate entrance facilities and pathways to its intended termination.
Meet-me room boundary
The meet-me room organizes carrier handoff and cross-connects, but a single room can become a shared physical fault domain.
Mechanism: Terminate external services in a controlled interconnection space before extending them toward network and tenant equipment.
Leaf-spine fabric
A leaf-spine fabric creates repeatable east-west paths when every leaf reaches every spine and the routing design uses those paths.
Mechanism: Connect access leaf switches to all spine switches while keeping same-role switches out of the forwarding path in the basic fabric.
Three-tier network
Access, aggregation and core layers create distinct network roles, but traffic paths and oversubscription depend on the actual design.
Mechanism: Connect endpoints at an access layer, consolidate policy and paths at aggregation, and provide broader connectivity through the core.
Top-of-rack switching
Top-of-rack access keeps server links short and repeatable while increasing the number of rack-level switches to power, cool and manage.
Mechanism: Place access switches in or near each rack and aggregate their uplinks into the wider fabric.
End-of-row / middle-of-row switching
Row-level access can consolidate switches and ports, but it moves more endpoint cabling into shared horizontal pathways.
Mechanism: Serve several racks from access switches placed at a row or zone location instead of inside every rack.
Independent A/B fabrics
Dual-attached endpoints gain useful resilience only when fabrics, border paths, controls and change processes preserve independence.
Mechanism: Connect eligible endpoints to separately defined network paths and make the workload or host behavior use them correctly.
Fire & life safety
Separate detection, containment, water systems and supplemental agents without turning generic reference into a code decision.
Compartmentation and penetration sealing
Fire-resisting boundaries work only when doors, cable penetrations, joints and later changes preserve the intended compartment.
Mechanism: Use rated construction and protected openings to limit fire and smoke spread for the adopted building and fire strategy.
Early-warning smoke detection
Air-sampling or other early-warning detection can reveal an incipient condition, but response depends on sampling design and cause/effect logic.
Mechanism: Continuously draw or sense air at designed locations and map alarm stages to investigation and approved system actions.
Wet-pipe sprinkler system
Wet-pipe systems keep water in the piping for direct thermal-element operation, with local design and acceptance governing application.
Mechanism: Maintain pressurized water in the system so an individual sprinkler can operate when its thermal element reaches its rated condition.
Dry-pipe sprinkler system
Dry-pipe systems hold pressurized gas in piping until sprinkler operation releases the valve; they are not the same as preaction.
Mechanism: Use gas pressure to hold a dry-pipe valve closed until an operated sprinkler reduces pressure enough for water admission.
Preaction sprinkler system
Preaction adds detection and release logic to a sprinkler system; single- and double-interlock arrangements are not interchangeable.
Mechanism: Control water admission to system piping through a defined detection and valve-release sequence before sprinkler discharge conditions are met.
Clean-agent suppression layer
A clean-agent system can supplement a fire strategy, but it requires life-safety controls, room performance and an approved recovery plan.
Mechanism: Detect and confirm a condition, execute the approved release sequence, and establish the agent concentration and hold behavior designed for the enclosure.
Rack & IT interface
Treat the rack as the interface between space, weight, power, cooling, cabling, security and service access.
19-inch equipment cabinet
A familiar 19-inch mounting interface does not by itself settle cabinet depth, load, airflow, cable space or service clearances.
Mechanism: Support compatible rail-mounted equipment inside a cabinet whose enclosure, doors and accessories coordinate the room interfaces.
Open Rack interface
Open Rack integrates mechanical, power and cooling interfaces for compatible gear, but it is a distinct ecosystem rather than a drop-in label.
Mechanism: Use the published rack, equipment-bay, busbar and optional cooling interfaces as a coordinated hardware platform.
Rack airflow accessories
Blanking panels, brush strips, doors and chimneys shape the airflow path only when they match equipment direction and room strategy.
Mechanism: Block bypass and recirculation openings or guide exhaust so the rack participates in the intended supply-and-return path.
Liquid-ready rack interface
A liquid-ready rack coordinates manifolds, hoses, leak response, service access and residual airflow rather than merely adding pipework.
Mechanism: Provide controlled supply and return interfaces from the facility or CDU boundary to compatible rack or server cooling loops.
How to read the evidence
Source-backed cards have a current public claim trail. Review-open cards remain visible as useful drafts while technical or source-rights review is pending. Every interactive lab labels its boundary, assumptions, limitations, model version and result type.