Skip to content
TechnoGuru — Think Technology, Think TechnoGuru

/ BMS

UPS runtime: the misconceptions that turn a 30-minute spec into a 12-minute reality

By Pranab Kumar BeriyaFounder & Chief Executive Officer·Published 21 May 2026·8 minute read·BMS

Quick answer

UPS runtime is the most over-specified and under-engineered number in the building's power layer. The catalogue figure assumes nameplate kVA at unity power-factor, fresh batteries at 25°C, and the published Peukert exponent for the battery chemistry. Real holdover at 30 months is typically 60-70% of catalogue for VRLA banks, 80-90% for LFP — driven by battery degradation curve, actual operating temperature (every 10°C above 25°C halves VRLA life), actual load power-factor (PoE switches and Wi-Fi 6 APs run at 0.9-0.95 PF, not 1.0), and the Peukert effect on high-discharge events. Per-load UPS sizing is uptime engineering; shared-bus UPS is power-quality engineering. The brief decides which is right.

UPS runtime is the spec that survives in the building's nameplate but rarely survives in the building's operation. The catalogue figure is a clean-room test result; the building's holdover at month 30 is what the operator actually has when the mains fails. The gap is engineered, not bridged after the fact.

## Battery chemistry decides the degradation curve

VRLA (sealed lead-acid) is the workhorse of mid-tier UPS deployments — cheap, well-understood, predictable. The degradation curve is also well-understood: 5-8% capacity loss per year under nominal conditions, accelerating to 12-15% per year above 30°C ambient. A 30-minute autonomy bank at year one is a 22-minute bank at year three and a 14-minute bank at year six. The AMC schedule treats VRLA banks as a 3-year refresh cycle for any holdover-critical load.

LFP (lithium iron phosphate) carries a much shallower degradation curve — 2-3% capacity loss per year under nominal conditions, 5,000-7,000 cycle service envelope at 80% DoD. A 30-minute LFP autonomy at year one is 27-28 minutes at year five and 24-25 minutes at year ten. The capex penalty is real (2.5-3× VRLA at parity capacity), but the lifecycle economics favour LFP for any deployment with 15+ year planning horizon.

## Temperature is the silent runtime killer

Battery cabinet temperature is the leading silent factor in runtime collapse. Every 10°C above 25°C halves VRLA service life; LFP is less sensitive but still de-rates above 35°C. UPS battery cabinets in tropical-climate buildings without dedicated cooling routinely operate at 35-40°C, which compresses the published 5-year VRLA life to 2-2.5 years. Battery-room HVAC is sized against the full-discharge thermal envelope, not the standing-charge load.

## Power-factor reality vs catalogue assumption

UPS nameplate kVA is published at unity power-factor (1.0). Real loads have lower power-factor: modern PoE switches and Wi-Fi 6 APs run at 0.9-0.95 PF, AV-over-IP encoders at 0.85-0.92 PF, server-class loads at 0.85-0.95 PF. A 10 kVA UPS at unity PF delivers 10 kW; the same UPS at 0.9 PF delivers 9 kW. The runtime calculation must use the actual load wattage at the actual PF, not the nameplate kVA.

## Peukert effect on high-discharge events

The Peukert exponent describes how battery capacity degrades non-linearly with discharge rate. A 100 Ah battery discharged at the 20-hour rate delivers 100 Ah; the same battery discharged at the 1-hour rate delivers 50-60 Ah depending on chemistry. High-discharge events (full-load UPS discharge during a sustained outage) consume more battery capacity than the nominal calculation suggests. The Peukert correction is built into proper UPS runtime calculators; the spec-sheet runtime is the nominal-rate figure, not the high-discharge corrected figure.

## Per-load UPS vs shared-bus UPS

Per-load UPS architecture puts every critical load class on its own dedicated online UPS — a fault on one load cannot cascade across the stack. Shared-bus UPS routes everything through one mainline UPS, cheaper capex and a single point of failure. The brief decides which is right: when uptime is the brief (perimeter security, command-and-control, medical-imaging), per-load is correct; when power-quality is the brief (data centre, broadcast), shared-bus with full redundancy is correct.

## AMC discipline is what preserves the runtime spec

VRLA battery autonomy tests at quarterly intervals — battery bank discharged under measured load, runtime measured against the spec, replacement triggered at 80% of spec. LFP autonomy tests at semi-annual intervals with the cell-level capacity baseline preserved. The test is the operational deliverable; without it, the runtime spec is theoretical and the first sustained outage is also the first discovery.

## Configuration baselines are part of the spec

UPS configuration (inverter mode, ECO mode, battery-test schedule, alarm escalation thresholds) is exported offline at handover and re-exported after every firmware refresh. A clean-slate UPS recovery within the same business day is the operational guarantee; without the configuration baseline, the recovery is hours of vendor-mode reconfiguration.

## Callout — what UPS procurement most miss

**Runtime spec is not runtime delivered.** The catalogue figure is the starting point; the AMC discipline, the battery-cabinet thermal envelope, the actual load power-factor and the Peukert correction together decide what the building actually has when the mains fails. Engineer against the delivered runtime, not the nameplate.

## References

1. IEC 62040-1 — uninterruptible power systems (UPS).

2. IEEE 1184 — guide for batteries for uninterruptible power supplies.

3. NFPA 110 — emergency and standby power systems (international cross-reference).

4. Peukert's Law — battery discharge-rate to capacity relationship.

Per-load UPS vs shared-bus topology

ups-ats-redundancy
Per-load UPS vs shared-bus UPS topologyPer-load UPS architecture (left): each critical load class — UVSS, X-ray, boom, turnstile, bollard — sits on its own dedicated online double-conversion UPS so a fault on one load cannot cascade across the stack. Shared-bus architecture (right): one mainline UPS feeds every load, so a fault or maintenance event takes the entire stack offline. The per-load architecture costs more capex but enforces fault containment at the power layer rather than the application layer.UPS topology · per-load vs shared-bus · uptime engineering, not power-quality engineeringPer-load enforces fault containment at the power layer · shared-bus collapses on a single eventPower hierarchy · upstreamUtility · DG · ATS · stabilizerUtility feedGrid transformerDG standbyN+1 poolATSAuto transferMain stabilizer8 kVA · X-ray gateEarthing pit ×4Chemical · plant-boundSurge protectionType 1 + 2Per-load UPS architecture · uptime engineeringEach load class on its own UPS · fault isolation enforced at power layerUVSS UPS3 kVA · 1 h holdUVSS loadUnderside cam · ANPRX-ray UPS6 kVA · 1 h holdX-ray loadGenerator · detectorBoom UPS2 kVA · 1 h holdBoom loadMotor · interlockTurnstile UPS2 kVA · 1 h hold (× 8)Turnstile loadFlap-gate × 6 lanesBollard UPS10 kVA · 1 h holdBollard loadHydraulic / electricShared-bus architecture · power-quality engineeringOne mainline UPS · single event takes every load offlineSingle mainline UPSSingle point of failureBattery refresh / fault drops the whole stackUVSS (shared)X-ray (shared)Boom (shared)Turnstile (shared)Bollard (shared)Cascading failure across the whole stackSingle UPS fault = perimeter screening offlinePer-load UPS is uptime engineering — a fault on the X-ray load cannot pull the boom barrier offline · the AMC inventory holds a named pack per load classShared-bus is power-quality engineering — cleaner sine wave, single point of failure · the brief decides which architecture is right, not the catalogue
Per-load UPS architecture (left) puts each critical load class on its own UPS with one-hour holdover — uptime engineering. Shared-bus (right) is cheaper capex and a single point of failure.

Key engineering takeaways

  1. Catalogue UPS runtime assumes nameplate kVA at unity PF, fresh batteries at 25°C — real holdover at month 30 is typically 60-70% of catalogue for VRLA, 80-90% for LFP.
  2. Battery cabinet temperature is the leading silent runtime killer — every 10°C above 25°C halves VRLA life.
  3. Modern PoE / Wi-Fi 6 / AV loads run at 0.85-0.95 PF, not 1.0 — the runtime calculation uses actual load wattage at actual PF.
  4. Peukert effect compresses delivered capacity on high-discharge events — proper sizing applies the chemistry-specific correction.
  5. Per-load UPS is uptime engineering; shared-bus UPS is power-quality engineering — the brief decides, not the catalogue.
  6. Quarterly VRLA autonomy tests and semi-annual LFP cell-baseline tests are the AMC discipline that preserves the runtime spec.
  7. UPS configuration baseline export at handover and after every firmware refresh enables same-business-day clean-slate recovery.

/ Frequently asked

Quick answers from the practice.

How often should VRLA banks be replaced?
Every 3 years for any holdover-critical load on the AMC schedule, regardless of measured capacity at the 3-year point. The cost of replacement is decisively lower than the cost of a sustained outage on a degraded bank.
Is LFP worth the capex penalty?
For any deployment with 15+ year planning horizon, yes — the lifecycle economics favour LFP decisively. For shorter-horizon scope, VRLA on a 3-year refresh remains the right answer.
How is the actual load wattage measured?
Per-circuit measurement at handover under a representative load envelope — the measurement informs the runtime calculation and the per-load UPS sizing. The catalogue nameplate is a starting point, not the operational figure.
Does TechnoGuru run quarterly UPS autonomy tests?
Yes — as part of every Gold and Mission-Critical AMC tier. Battery bank discharged under measured load, runtime measured against the spec, replacement triggered at 80% of spec. The test record is in the AMC log.

/ What to do next

Three next steps for UPS scope

/ About the author

Pranab Kumar Beriya Founder & Chief Executive Officer

Founder of TechnoGuru; sixteen years of practice in residential cinema, automation and turnkey systems integration across eastern India and the wider sub-continent. AVIXA Certified, K-Array Designer, CEDIA Member, HAA Level 1 Calibrator, Rako-DALI trained, AMX-certified, Harman BSS programming-certified, Alcatel-Lucent OXO Connect-certified.

/ Discuss your project

If this article matches a brief you are working on, the next step is a thirty-minute call with a project lead.

We do not run sales pipelines. The first reply comes from a project lead, within two working days, and it goes straight to the engineering question rather than a brochure.

Begin a brief
UPS runtime: the misconceptions that turn a 30-minute spec into a 12-minute reality | TechnoGuru