Data Center Design and Standards
What this domain tests
Data Center Design and Standards tests whether you can turn a business availability requirement into a physical topology and defend it against a recognised standard. Expect questions comparing ANSI/TIA-942-B, ISO/IEC 22237 (which absorbed EN 50600), BICSI 002 and the Uptime Institute Tier scheme, plus classification of a described facility.
Tier and class logic
Tier I is basic capacity; Tier II adds redundant capacity components; Tier III is concurrently maintainable; Tier IV is fault tolerant. The testable distinction: Tier III allows any component to be maintained without affecting the IT load; Tier IV also survives an unplanned fault in the distribution path. Topology, not a bill of materials, determines the tier.
Redundancy vocabulary
N is the load; N+1 adds one spare component; 2N duplicates the whole path; 2(N+1) duplicates with a spare in each path. Concurrently maintainable, fault tolerant and fault resilient are different claims. Availability is A = MTBF / (MTBF + MTTR), so reducing MTTR through good operations can raise availability as much as adding hardware.
Design sequence and documents
Requirements (IT load, growth, availability, efficiency) -> site selection -> architectural and structural -> power and cooling capacity -> topology -> fire, security and cabling -> commissioning criteria. Deliverables include the basis of design, single-line diagrams, load schedules, CFD airflow models and a tier statement.
Worked example
A client demands Tier III for 1,000 kW of IT load. The proposal shows two 1,000 kW UPS modules (N+1) feeding a single PDU bus. Is it Tier III? No. Although the UPS is redundant, the downstream distribution is a single path, so maintaining the PDU or its bus requires de-energising the load. Fix: dual-corded IT loads fed from two independent UPS outputs through separate PDUs and panels with isolation, or rack-level ATS/STS for single-corded equipment. The tier is set by the weakest point in the chain.
Traps that cost marks
Assuming 2N is mandatory for Tier IV; confusing component redundancy with topology; mixing EN 50600 classes with Uptime tiers; forgetting that standards are voluntary unless written into a contract; omitting non-IT loads (cooling, fire, security, fuel transfer) from the capacity calculation.