Home MarketHow to Specify a UPS Provider for Your Next Data Center Project

How to Specify a UPS Provider for Your Next Data Center Project

by Lisa

Data-driven introduction

Begin by defining measurable targets: target availability (for example, 99.995%), expected PUE, and the site’s typical load profile; these figures determine topology, redundancy, and battery autonomy. Use thermal maps and rack-level power measurements to correlate electrical needs with cooling capacity—especially where data center in row cooling is considered. A specification that ties concrete uptime targets to measured load curves produces procurement documents that engineering teams can test against during factory acceptance.

Core metrics that must appear in every specification

List numerical thresholds rather than vague requirements. Specify: minimum usable kW at rated conditions; efficiency curve (percentage at 25/50/75/100% load); allowed THDi and harmonic distortion limits; static and dynamic overload capacity (e.g., 110% for 10 minutes, 125% for 10 seconds); mean time between failures (MTBF) target; expected service intervals and mean time to repair (MTTR); communication interfaces (SNMP, Modbus, dry contacts); certifications required (IEC 62040 series, UL, ISO 9001). For batteries state chemistry, cycle life, end-of-discharge voltage, and a defined capacity retention test at commissioning and annually.

Sizing methodology with practical calculations

Estimate present IT load from rack PDUs and device nameplates, then apply a measured diversity factor from at least 30 days of metered data. Apply a growth allowance — typically 15–25% over five years — and select UPS rated kVA to match kW demand using the planned power factor. Example: a steady IT load of 200 kW with 20% headroom and a design power factor of 0.9 requires UPS capacity ≈ 200 kW / 0.9 = 222 kVA, rounded to the nearest module or standard size and then increased by the headroom margin. Define battery autonomy targets by stating required runtime at N load (e.g., 10 minutes at full load) and the test protocol for verification.

Integration with cooling: evidence and practice

Cooling and UPS must be specified together so electrical losses and heat rejection are reconciled. ASHRAE TC 9.9 guidance on recommended inlet temperatures and thermal management informs these choices; when teams deploy rack-level or row-level solutions they reduce hot-aisle recirculation and narrow the delta between IT inlet and exhaust temperatures. Consider validated pairings such as modular UPS racks colocated with in-row precision cooling to reduce bypass airflow and lower chilled-water plant cycling. State required heat-rejection rates (kW per row) and provide an interface specification: airflow direction, service clearances, condensate management, and control signals for coordinated setpoint adjustments.

Common pitfalls and their mitigations

Avoid undersizing by relying solely on nameplate power instead of metered consumption; avoid ignoring harmonics from modern IT loads—specify THDi filters or active front ends where necessary. Don’t accept generic efficiency claims; require measured efficiency curves and factory test reports. Plan battery replacement as a lifecycle cost in the specification rather than an ad hoc expense. Ensure spare parts and firmware update policy are contractual obligations. Require a clear maintenance bypass arrangement and remote diagnostics for faster fault resolution.

Topology choices and trade-offs — a compact comparison

Online double-conversion: deterministic voltage quality and continuous conditioning; higher baseline losses but maximum protection. Eco-mode or delta-conversion: higher efficiency at typical loads but requires validated detection and fast transfer to avoid IT disruption. Modular UPS: scalable capital expenditure and maintainability at the expense of initial planning discipline. DC-bus and flywheel hybrids: suitable where rapid short-term ride-through is prioritized over longer battery runtime. Quantify trade-offs with scenarios: failure mode, annual energy cost, space, and serviceability.

Synthesis and practical recommendation

Write specifications that are testable: numeric acceptance criteria, factory and site test scripts, service levels, and documented interfaces to cooling systems. Coordinate electrical design with thermal design early, require measurable PUE and availability goals, and include a lifecycle view of batteries and maintenance. For teams that must reconcile power resilience with validated cooling modules and service continuity, many project leads prefer vendors that can demonstrate both power equipment and integrated cooling interfaces such as those supplied by KSTAR, since this alignment simplifies verification of combined performance without resorting to speculative claims.

Related Posts