Rack Power Planning: PDUs and Load

What does rack power planning cover, and where does it stop?

On paper, before the build, rack power planning catches the overloaded feed and the missing outlet while they are still free to fix.

It is deciding how a rack gets powered and writing it down: what each device draws; which power distribution unit (PDU) feeds it; how the PDUs are arranged; the order the rack comes up in; how power stays clear of signal.

It stops at a hard line. Reading nameplates is documentation any AV planner can do. So is totaling load per feed. So is mapping outlets. So is planning bring-up order. Then there is the other side: sizing the circuit; choosing the breaker; balancing phases; bonding or grounding the rack. All of that is electrical design, and it belongs to the licensed trade.

Step 1, Document the load for every device

Power planning starts with an inventory, like signal planning, except the number you record is each device's power draw. Read it off the nameplate or datasheet. Not from memory. The nameplate figure is the manufacturer's rated draw, commonly a worst case the device rarely reaches. That is why you plan on it: the rack has to survive the worst legal moment, and the average one is not the number to plan against.

Two figures cause most of the confusion. Devices are rated in watts (real power) or in volt-amps, VA (apparent power). For switch-mode supplies the two are not equal. If a datasheet gives one and your electrician needs the other, the bridge is the power factor on the datasheet. Record whichever they ask for, and note the device's expected voltage while you are there.

How do you total the rack load without inventing numbers?

Totaling is addition, done per feed. Not per rack. Sum the nameplate draw of every device on a given PDU or supply, keep watts and VA in separate columns so you never add apples to oranges, then leave headroom for the gear that shows up on site: the result is a set of per-feed load numbers, and that is where your job ends and the electrician's begins.

Per-feed load = sum of every device's nameplate draw on that feed
Mixed units: convert with the datasheet power factor, VA = watts / power factor
Add headroom above the computed total for on-site additions and a margin of safety
Hand the per-feed total to your electrician, who applies continuous-load and local-code rules to size the circuit and breaker

Where do PDUs go in the rack, and how many?

One feed in, many outlets out: that is a PDU. Where it sits follows the rest of the layout. Power distribution lives low and close to where power enters the case, so the feeder run inside stays short. Placement order is covered in designing a rack elevation. Here the question is what the PDU is and how many the rack needs.

PDUs come in tiers, and picking a tier is a planning choice rather than an electrical one:

• Basic PDU: outlets and nothing else, cheapest and lightest, with no visibility into the draw.
• Metered PDU: reports total draw on a display or over the network, so you see a feed nearing its planned load instead of finding out at the breaker.
• Switched PDU: powers outlets on and off remotely, handy for rebooting a frozen device in an unattended rack.
• Per-outlet metered: draw reported outlet by outlet, the most documentation for the most money.

How many PDUs? That depends on the number of feeds and how you group outlets. A single-feed rack may need one. A dual-feed rack, at least one per feed. Whatever the count, map every outlet to the device it powers, so a dark switch is a glance at the plan instead of an investigation. Leave a few spare outlets drawn in as real capacity, or the rack grows a zip-tied power strip by the second gig.

Should the rack have redundant power?

Redundant power means a device keeps running if one supply dies; it is worth planning when the rack carries something a show cannot lose, and it comes in a few concept-level forms:

• Dual-PSU gear on separate feeds. Many switches have two supplies. So do some servers and processors. They ride through a lost feed only if the supplies land on different feeds. Both on one feed defeats the point.
• UPS for ride-through, not for running the show off a battery. It covers the gap while a generator catches or a feed returns. It gives critical gear a graceful shutdown. Runtime? A datasheet number tied to the load.
• Protect the gear that must not reboot. Processors. Switchers. Control. Keeping them on power the rest of the rack cannot drag down is common practice: a fault on a hungry amplifier should not reboot the device feeding it.

Where the feeds come from is distribution design. So is how they transfer, and so is how they are protected. None of it is a diagramming task. Plan which devices need redundancy and on which feed. Let the electrician deliver the feeds, and read UPS runtime off the datasheet against your load.

Power-on sequencing: bring the rack up in order

When many devices energize at once, their supplies can briefly draw well above steady state while capacitors charge. Stack that inrush across a whole rack switched on together, and a feed that carries the show fine can trip at the flip. A power sequencer brings the rack up in stages. So does a switched PDU used deliberately.

Order also protects the system. A long-standing audio practice powers amplifiers up last and shuts them down first. The thump of everything upstream settling never reaches the speakers that way. How much inrush your specific gear produces is a datasheet question. The planning takeaway: power-on is its own load case that deserves a documented order, written on the rack plan rather than kept in someone's head.

Keep power and signal on separate paths

Power planning and cable planning meet here. Run AC and power down one side of the rack and low-level signal (audio, control, data) down the other, crossing at 90 degrees where a power run and a signal run must meet. This is EMI hygiene rather than superstition. Parallel power and signal is how induced hum and noise get in, and the classic victim is unbalanced analog audio. Separation gets decided when you plan the power, since it constrains where the PDU and its whip go. The dressing detail lives in rack cable management.

Document it so the electrician gets numbers, not a shrug

A clean handoff is a short, specific package rather than a drawing they have to interpret. Give the electrician the per-feed load totals; the device list behind them; the outlet map; the supply you expect on site. With real numbers they can size the circuits and breakers. They can confirm the rack is safe. Very different conversation from handing over a shrug and a photo.

All of that is documentation, where one source of truth pays off. WireFlow's rack builder places gear to RU scale. It records which device lands on which PDU outlet as its own layer. It exports install-ready PDFs, so the outlet map and the elevation cannot drift apart. Because the rack shares a project with the signal-flow diagram, the gear list and cable schedule travel with it into one tech pack your electrician and crew both read from. The internal wiring layer and RU counting are covered in rack internal connections and rack units and equipment.

Frequently asked questions

What is rack power planning?

The preproduction step of documenting how an AV rack is powered: each device's nameplate draw; the per-feed total; which PDU and outlet feeds each device; the power-on order; how power stays clear of signal. It produces load numbers and an outlet map. Circuits it does not size. Breakers either. That is a licensed electrician's job under local code.

How do I calculate the power load of a rack?

Sum each device's nameplate draw per feed. Keep watts and VA in separate columns since they are not the same thing, and convert with the datasheet power factor when you must. Add headroom for gear added on site. Then hand that per-feed number to your electrician, who applies continuous-load and code rules to size the circuit. No amperage target should come off the drawing itself.

Where should the PDU go in a rack?

Low in the rack, close to where power enters the case, so the feeder run stays short. That lines up with placing the heaviest gear low. Use at least one PDU per feed. Map every outlet to the device it powers. Basic or metered or switched is a planning choice about how much visibility and remote control you want.

Do I need to separate power and signal cabling in a rack?

Separate what you can, even in a small rack. Run power down one side. Run low-level signal down the other, crossing at 90 degrees where they must meet. Parallel power and signal is how induced hum and noise get in, and unbalanced analog audio and long control runs suffer first. It costs nothing at build and saves a noise-chase after the rack is closed up.

Build your rack elevation in WireFlow

Drag gear into front and rear rack views, document internal patching, and export install-ready PDFs.

Open the rack builder · Start free