Rack power budget worksheet: turn an equipment list into a reviewable plan

A useful worksheet records assumptions as well as totals

A rack power budget should explain what equipment is included, where the numbers came from and which limits constrain the arrangement. A single total labeled rack watts is not enough to support a purchase. Keep current operating demand, approved growth, required failure scenarios and manufacturer ratings in separate fields so a reviewer can see what each number means.

Begin with one row per equipment asset and additional rows where separate power supplies need individual outlet mapping. Give the worksheet a date, owner and configuration reference. Include the rack identifier and the source or UPS being evaluated. These details prevent a worksheet for one installation from being reused after equipment has moved without anyone noticing the changed assumptions.

The worksheet is a decision aid, not an electrical installation design. The facility owner supplies the approved source information, while equipment owners supply the workload and availability requirements. Mark missing information as unresolved. A blank source-limit field is more useful than a guessed value that makes the total appear to pass.

Build the inventory around actual powered equipment

Include servers, storage, switches, management appliances and any accessories receiving power through the same UPS or PDU. For a PoE switch, ensure the estimate includes the power delivered to attached devices when those devices belong in the protected-load requirement. Avoid counting that delivered power twice if the switch’s total input figure already includes it.

Record the evidence for each load: a relevant measurement, a manufacturer configuration estimate or another documented planning input. State the workload and measurement boundary. A chassis power-supply capacity is an output capability, not automatically the input consumption of the equipment during normal operation. Two fitted power supplies likewise do not by themselves double the asset’s consumption.

Keep any uncertainty explicit. A new server not yet delivered may need a vendor configuration estimate, while an existing switch may have observed input demand. Those can share a worksheet without pretending they have identical certainty. Update the provisional row when suitable operational evidence becomes available through the approved deployment process.

Use a worked inventory to see the arithmetic

Consider the illustrative inventory below. Every load value is invented for explaining the worksheet and should be replaced with evidence for the actual equipment. Two servers are budgeted at 360W each, storage at 120W, a switch including its planned powered devices at 70W and a management appliance at 20W. The current planning total is 930W.

The table keeps quantity separate from the per-device assumption so multiplication remains visible. If the servers differ, give them separate rows rather than hiding the difference in an average. Add an evidence reference and an owner in the working version. A total that can be reconstructed is easier to correct when one asset changes.

Suppose the approved next stage adds another 300W of protected equipment. Record that as a distinct planned addition, producing a future total of 1,230W. Do not silently blend it into today’s operating figure. The two scenarios answer different purchasing questions: whether the present arrangement meets the requirement and whether it can support the approved expansion.

Keep watts, VA and current in their own columns

APC distinguishes real power in watts from apparent power in volt-amps. The UPS must satisfy both applicable output limits, while the manufacturer’s runtime chart commonly asks for watts. APC’s buying guide explanation supports maintaining separate units rather than using VA as another name for measured consumption.

For a single-phase illustrative calculation at 120V with an assumed aggregate power factor of 0.95, 930W corresponds to about 979VA and 8.2A. The formulas are apparent power equals watts divided by power factor, and current equals apparent power divided by voltage. The power factor and voltage here are stated assumptions, not verified values for the listed equipment or an installation approval.

Use actual manufacturer data or suitable measurements for the deployed load and follow the source owner’s approved limits. Do not assume that an individual device’s maximum label current is its typical consumption, or use an optimistic power factor to make a constrained design pass. Where the information is uncertain, retain the conservative planning basis accepted by the responsible reviewer.

Make a second table for the limiting equipment

Record each proposed UPS’s watt and VA output limits, each relevant output-group limit, PDU total and bank limits, individual connection limits and the facility’s approved source capacity. Keep manufacturer ratings separate from the load rows. A PDU with many unused receptacles can still be constrained by its input, and a higher rated PDU cannot enlarge the UPS output feeding it.

For a concrete capacity check, Schneider specifies the SMT1500RM2UC at 1,000W output. The illustrative 930W load is below that watt limit alone, while the future 1,230W load exceeds it. The exact UPS specification supplies that rating. Passing the first comparison does not establish acceptable VA, current, distribution, runtime or growth margin.

Add a result column for each gate: supported, unresolved or outside the stated limit. Include a source URL or document reference beside the limit. If a manufacturer page and a supplied data sheet conflict, obtain clarification for the exact product rather than selecting the larger number. The worksheet should expose the conflict before it affects a purchase.

Budget the load after the required failure

For a rack with A and B paths, add separate scenario columns for normal operation and the required source-loss cases. Map each equipment supply to its source and state the expected behavior. Do not assume that normal readings split exactly in half or that each path only ever needs its observed normal share.

Dell documents hot-spare configurations in which most demand is placed on active supplies, and distinguishes supported redundancy arrangements. Its PowerEdge power settings guidance reinforces the need to record actual equipment settings. A worksheet based on assumed equal sharing can misrepresent both the normal load and the surviving-path requirement.

For an illustrative pair of dual-supply servers totaling 720W, an approved failover scenario may require one path to carry the full 720W plus other loads already assigned there. Review every applicable limit and the UPS runtime at that resulting load. If the service requires full performance, confirm that the equipment’s supported redundant configuration meets that requirement as well.

Attach a runtime and shutdown timeline to each scenario

For each UPS configuration, read the manufacturer’s estimate at the relevant protected watt load and battery-module count. Keep current, future and required failover estimates separate. A runtime value at 500W should not be pasted into the 930W row merely because the UPS model has not changed.

Then document what the battery time must cover: detection delay, application work, host shutdown, storage completion and an appropriate planning reserve. The service owner provides the accepted timeline. Keep it distinct from the manufacturer’s estimate so a reviewer can see both the requirement and the available reference duration.

Use the equal-watt runtime guide to compare candidates consistently. Preserve the exact model, battery configuration and source date with each result. Treat the published estimate as a planning reference and include supported validation of the deployed shutdown workflow in the implementation scope.

Use the worksheet when equipment changes

Before accepting an addition, identify its owner, evidence, intended outlet and impact on current, future and failure totals. Recheck any constrained bank or source. If the new equipment changes the shutdown dependencies, update the service timeline too. A power budget is most useful at the moment a proposed change can still be adjusted.

Keep a versioned record of the accepted worksheet and the source map. After deployment, reconcile the installed equipment and suitable operational readings with the plan. Investigate material differences with the relevant owners instead of quietly replacing the estimate with whichever number is smaller. The evidence trail should show why the planning basis changed.

The finished worksheet should let another reviewer answer five practical questions: what is powered, what it is expected to draw, where it is connected, which limit matters and what happens in the required failure scenario. Use the UPS-to-PDU guide for connection checks and keep the approved facility information beside the worksheet. That makes the budget reusable without turning assumptions into undocumented permissions.

Sources and research basis

• APC UPS buying guide, watts and volt-ampsPrimary documentation · checked 15 October 2026
• APC SMT1500RM2UC official product specificationsPrimary documentation · checked 15 October 2026
• Dell PowerEdge power settings and hot sparePrimary documentation · checked 15 October 2026

Manufacturer specifications describe the documented configuration. Buying recommendations are our interpretation of those features. No original runtime, acoustic, efficiency, switching or software test is claimed. Report a correction.