Circuit Limits and Load Planning
Every PDU in a rack connects to a circuit. That circuit has a rated load capacity — typically expressed in amperes — and that capacity is shared across everything connected to it. In environments where racks are shared between different systems, or where hardware has been added incrementally over time, the total load on individual circuits is frequently not accurately tracked.
The consequence is circuits operating at or above their rated capacity. Tripped breakers under load cause unplanned downtime. Overloaded circuits that do not trip immediately represent a sustained safety risk. In either case, the root cause is load planning that treated circuit capacity as a background assumption rather than a design constraint.
Before a rack is populated, the total power draw of all planned equipment — including typical operating load and peak load — must be calculated and compared against available circuit capacity. This calculation must account for future growth, not just the immediate hardware list.
Redundancy and UPS Environments
Many infrastructure environments operate with N+1 or 2N power redundancy at the rack level: dual-corded servers, dual PDUs fed from independent circuits, UPS protection on both paths. The design intent is that no single power failure causes an outage. In practice, redundancy is frequently compromised during installation or subsequent changes.
Dual-corded equipment wired to two PDUs that share the same upstream circuit is not redundant. UPS devices that have never been load-tested may not support their rated output under real conditions. Bypass circuits that are undocumented mean UPS maintenance requires taking systems offline unplanned. These are common conditions in technical rooms where power infrastructure has grown incrementally without consistent documentation.
Understanding the UPS environment means knowing the rated capacity of each unit, its actual current load, its battery test records, the circuit protection between it and the distribution board, and what it is intended to cover. That information must be documented and accessible to the operations team.
Fusing and Power Paths
The path from a distribution board to a rack-level PDU outlet passes through multiple protection points: main distribution fuses or breakers, sub-distribution boards, PDU input fusing, and in some cases intermediate protection within the rack. Each protection point must be rated consistently with the circuit design and with every other element in the chain.
In practice, circuits are sometimes extended or modified without reviewing the protection chain. A fuse rated too large for the cable it protects provides inadequate fault protection. In environments where documentation is incomplete, identifying the protection chain for a given circuit requires physical investigation — a process that should not be necessary in a professionally managed infrastructure.
For high-density systems and AI workloads, this matters directly. High-draw equipment connected through an incorrectly rated or undocumented protection chain creates conditions that no PDU selection can compensate for. The engineering must start above the PDU, not at it.
Documentation and Change Records
Rack power infrastructure that is not documented cannot be operated safely by anyone who was not present during its installation. Circuit assignments, PDU port allocations, power draw per outlet, protection chain details, and UPS coverage scope all need to be recorded and maintained.
Change records are equally important. When equipment is added to a rack, the PDU load record must be updated. When a circuit is modified, the documentation must reflect the new state. When a UPS is replaced or reconfigured, the coverage map must be current.
Power documentation is not a post-project deliverable — it is an ongoing operational record that supports safe operation, fault diagnosis, and future planning.
The Planning Discipline
Rack power planning is an engineering discipline, not a procurement decision. The PDU is the visible outcome of decisions about circuit design, load distribution, redundancy architecture, protection chain consistency, and documentation practice. Getting the PDU right while leaving the underlying decisions unaddressed produces infrastructure that looks correct but operates with hidden risk.
The standard is clear: rack power is documented, load is tracked per circuit and per outlet, redundancy is verified as operational, protection chains are consistent, and UPS coverage is tested and recorded. That is the baseline for infrastructure that supports the systems running above it reliably.
