Battery and RuntimeUPS EngineeringPlanning

Specify UPS Runtime for a Time-Varying Load

By Highidea Power · 22 October 2026 · 3 min read

Conceptual engineering illustration: Specify UPS Runtime for a Time-Varying Load.

Specify a changing load as a sequence of simultaneous watts, VA and durations. Add the load-side energy of the segments, but retain the highest power requirement and transient events separately. An average wattage can describe energy demand while concealing a host-capacity problem. The resulting Wh total is a configuration input, not a battery nameplate requirement or a runtime guarantee.

Highidea's external-battery online UPS routes allow the host and storage arrangement to be discussed against an actual operating task. A staged schedule makes that discussion more useful than one average load number.

Start after the priority decision

First decide which functions must continue and which may stop under the site's approved plan. Our load-priority guide covers that operational decision. Here the next task is to turn the agreed sequence into a reproducible demand profile.

Use elapsed time from the outage start. For each interval record all active dependencies, stable W, simultaneous VA, duration and the evidence for each figure. Keep startup or shutdown transients alongside the interval rather than hiding them inside its average.

Work a complete staged example

Assume this hypothetical 30-minute task: an initial processing stage, a controlled reduction, and a final communications-only stage. Assume the listed powers are constant within each segment and the VA values are valid simultaneous totals for this example.

Interval

Demand and load-side energy

0–5 minutes

900 W, 1,100 VA; 900 × 5/60 = 75 Wh.

5–15 minutes

450 W, 600 VA; 450 × 10/60 = 75 Wh.

15–30 minutes

120 W, 180 VA; 120 × 15/60 = 30 Wh.

Complete task

180 Wh over 0.5 h, equivalent to 360 W average; highest listed steady demand remains 900 W and 1,100 VA.

A host chosen only for 360 W could fail the initial stage even if its storage contained enough energy. Conversely, meeting the 900 W peak does not establish the required 30 minutes. Both power and energy constraints must be satisfied.

These are invented load inputs, not Highidea measurements. No efficiency, battery capacity, startup demand or temperature allowance has been assumed.

Make delayed transitions visible

The schedule assumes the reduction occurs at five minutes. If the 900 W stage continues for another five minutes instead of the planned 450 W stage, the load needs an additional (900 − 450) × 5/60 = 37.5 Wh. The total becomes 217.5 Wh for the same overall interval.

That arithmetic identifies a scenario to review; it does not authorize delaying shutdown. Record the site's required case for a failed command, unavailable operator or missed transition. Include observable completion evidence and the approved fallback.

This one-off staged task differs from a recurring sampling-pump duty cycle. Its transition times and endpoint determine which segments must be supplied.

Convert demand into a configuration request

Give the supplier the segment table, W/VA evidence, transient requirements, stop criterion and permitted operating modes. The complete review then accounts for conversion losses, host consumption, usable battery range, temperature, aging assumptions and recharge duty.

Efficiency may vary with load. Do not apply a catalogue maximum to every segment without supporting conditions, or divide demand-side Wh by nominal battery voltage and treat the result as an approved pack size.

Use a controlled comparison record: required scenario, load schedule revision, offered host/storage, assumptions, supported result and unresolved owner. Retain both the normal schedule and relevant delayed-transition cases.

Discuss the profile with Highidea

Send Highidea the time-based schedule, required autonomy, installation format and expected recovery sequence. We can discuss the suitable product route using these inputs. Electrical operations and functional verification should follow the site's approved safe plan; do not create a live outage to populate the spreadsheet.

FAQ

Frequently asked questions

Can one average value replace the schedule?

It can summarize load-side energy over the stated interval, but it loses the timing, peak and transition information needed for selection.

Is the calculated Wh the battery energy to order?

No. The selected host/storage system must convert its usable energy into the required output under the agreed conditions.

Should generator pickup be treated as the end of the profile?

Only if it is the agreed service endpoint and the project establishes the required source and transfer conditions. Otherwise include the continuing task and recovery state. Preserve the duration assumption so a delayed pickup can be evaluated separately rather than silently shortening the battery-supported interval.

Put this into practice

Need help specifying the right unit?

Share the load, voltage, runtime, environment and destination for a configuration review.