Power & Runtime Planning Guide
A practical workflow for estimating UPS runtime, backup power needs, electrical load, battery sizing, power margin, and future growth before selecting equipment.
Use the guide as the written version of the power design flow
Power and runtime planning should be handled as a sequence, not as a single isolated calculator result. The connected load affects the required UPS size. The UPS load affects runtime. Runtime affects battery sizing. Growth margin affects all of those decisions. runtime and reserve assumptions determine whether the final plan is realistic.
This guide explains what each step means, when it matters, why it affects the next step, and where it fits in the ScopedLabs Power & Runtime workflow. The goal is to help you build a defensible planning estimate before comparing equipment, documenting assumptions, or reviewing manufacturer data.
Step 1 — Collect device load data
This step is where you build the equipment list for anything that needs backup power. For each device, collect the power information that is available: watts, VA, amps, voltage, current draw, power supply rating, PoE budget, or manufacturer-listed operating draw. The data will not always be listed in the same format, so the first job is to gather it clearly before converting it into a usable planning load.
For ScopedLabs-style planning, this usually means network, security, and IT equipment such as switches, PoE switches, routers, firewalls, NVRs, recording servers, access control panels, wireless radios, access points, small servers, storage devices, modems, ONTs, and other rack or closet equipment that must stay online.
This should happen before runtime, battery sizing, load growth, redundancy review, or scenario comparison. Every later calculation depends on the starting load estimate. If the equipment list is incomplete, the rest of the workflow can look more accurate than it really is.
Missing a device can make runtime look better than reality. Mixing watts, VA, amps, and power supply ratings without normalizing them can also distort the plan. A PoE switch, recorder, storage expansion, network appliance, or added radio may not look like much by itself, but together those loads can change the backup-power requirement.
The goal is not to design the electrical system. The goal is to create a defensible equipment-load baseline that can be carried into runtime, battery, reserve, and scenario planning.
This is the first step in the Power & Runtime guided flow. Use VA / Watts / Amps to convert mixed device ratings into a baseline load, then carry that baseline into Load Growth, UPS Runtime, and Battery Bank Sizer.
Step 2 — Convert watts, VA, amps, and power factor correctly
Watts describe real power. VA describes apparent power. Amps describe current at a given voltage. Power factor connects real power and apparent power. These values are related, but they are not interchangeable without knowing the voltage and the assumptions behind the load.
This step matters whenever the equipment list uses mixed units or when a UPS, inverter, power supply, or branch circuit is rated differently than the load you are estimating. It is common to see one device listed in watts, another in amps, and a UPS rating expressed in VA.
A runtime plan can look valid while still being based on incompatible units. For example, treating watts and VA as equal without considering power factor can hide apparent load. Using amps without voltage can also distort the estimate. Normalizing the units makes the rest of the workflow easier to explain and review.
Use Start Guided Flow after collecting the equipment list and before runtime planning. If conversion losses are part of the system, use Inverter Efficiency Estimate conversion losses and input power needs so runtime to keep usable output separate from input draw and efficiency losses.
Step 3 — Add growth margin before sizing equipment
Growth margin is the extra capacity reserved for future devices, equipment refreshes, added cameras, larger switches, storage expansion, or higher operating loads. It is not the same as guessing high; it is a documented planning allowance that keeps the system from being sized only for day one.
Growth matters when the system is likely to expand or when replacing equipment later would be expensive or disruptive. It is especially important for racks, network closets, surveillance systems, access control panels, small server rooms, and remote sites where adding backup capacity later may require new equipment or downtime.
A UPS that supports the current load may fall short after one equipment upgrade. As load increases, runtime usually drops. That means a design that looks acceptable today can become weak after adding devices. Growth planning helps show whether the system has room or whether it is already too close to the edge.
Add growth after the starting load is normalized and before runtime and battery sizing are finalized. Use Load Growth when you need to show how future load changes affect the planning baseline.
Step 4 — Estimate UPS runtime realistically
UPS runtime is the estimated time a backup system can support the connected load during an outage. It depends on load, battery capacity, inverter efficiency, battery condition, temperature, age, reserve margin, and the discharge behavior of the equipment being used.
Runtime matters once you know what equipment must remain online and how long it needs to operate. Short runtime may be enough for graceful shutdown or brief utility interruptions. Longer runtime may be needed for security systems, network continuity, recording systems, remote equipment, or sites that must bridge generator startup time.
Runtime is not a fixed property of the UPS. A small increase in load can reduce runtime sharply, especially when the system is already near its useful range. Planning runtime before checking load growth can lead to overly optimistic expectations. Manufacturer runtime charts still matter for final selection, but early runtime estimates can catch bad assumptions.
Runtime planning comes after load conversion and growth margin. Use Battery Sizing Estimate basic battery requirements to hit a target runtime with when you have a connected-load estimate and a target outage duration. Treat the result as a planning estimate that should be compared against manufacturer data before purchase.
Step 5 — Review battery sizing and reserve
Battery sizing estimates how much stored energy is needed to support the load for a target runtime. It considers usable battery capacity, system voltage, efficiency, discharge limits, reserve margin, and the fact that batteries age over time.
Battery sizing becomes important when runtime is a design requirement instead of a nice-to-have estimate. It matters for extended runtime systems, larger UPS deployments, inverter-backed loads, remote equipment, and any system where battery replacement cost or reserve capacity needs to be documented.
A battery system that works on paper can still be weak if the usable capacity, reserve margin, aging, or efficiency assumptions are unrealistic. Batteries also do not stay new forever. Planning with no reserve can make the system fragile as soon as conditions change or the battery ages.
Battery sizing comes after the load and runtime target are understood. Use Battery Sizing Estimate basic battery requirements to hit a target runtime with to review whether the battery assumptions support the target runtime with reasonable reserve.
Step 6 — Stress-test the runtime plan before equipment selection
Final runtime review means checking the load, growth margin, runtime estimate, battery reserve, redundancy assumptions, degraded conditions, and alternate scenarios as one planning package. This is not electrical design. It is a practical review of whether the backup-power assumptions still hold together before equipment is selected or documented.
This matters after the main guided flow is complete. Once the baseline load, projected growth, UPS runtime, and battery bank assumptions are known, the supporting tools can help answer “what if” questions before the plan is treated as final.
A single runtime estimate can look clean while hiding weak assumptions. Runtime may change if a battery string fails, redundancy reduces usable capacity, batteries age, conditions are pessimistic, or the project team compares multiple design options. Stress-testing the plan makes those assumptions easier to explain and defend.
Use this as the final planning-review layer after the core guided flow. Supporting tools such as Failure Runtime Loss, Redundancy Impact, Scenario Comparator, and Worst-Case Runtime help document what happens when the assumptions are not ideal.
Example workflow: small rack or equipment closet
A small rack may start with a router, firewall, PoE switch, camera recorder, storage, and a few supporting devices. At first, the power requirement may look simple. But if the site later adds cameras, a larger switch, extra storage, or a second network appliance, the load and runtime can change quickly.
The cleaner planning path is to list the connected load, normalize watts and VA, add a realistic growth margin, estimate runtime, then check battery and runtime assumptions. That sequence makes it easier to explain why a certain UPS size or battery reserve is reasonable instead of relying on a single calculator result.
Common power planning mistakes
This usually happens when the estimate is based on today’s equipment list without considering additions or refreshes. It matters because runtime falls as load grows. Catch it during the growth-margin step before the runtime estimate is treated as final.
This happens when equipment ratings, UPS ratings, and circuit assumptions use different units. It matters because the plan may look consistent while hiding apparent load. Catch it during the unit conversion step.
This happens when a planning estimate is treated like a manufacturer-certified result. It matters because batteries, load, temperature, age, and discharge behavior can change the outcome. Catch it by comparing estimates to manufacturer runtime data.
This happens when the battery plan assumes perfect new-battery behavior forever. It matters because real systems degrade. Catch it during battery sizing by keeping reserve and replacement planning visible.
Where the Power & Runtime tools fit
Use this section as the plain-English map of the Power & Runtime planning path. The guided flow covers the core sequence for load conversion, projected growth, runtime impact, and battery bank sizing. Supporting tools help validate related assumptions, but they are not required guided-flow steps.
Start here when you want the tools to work as a connected workflow instead of separate one-off calculators. This sequence builds from the device load baseline into growth margin, runtime impact, and battery reserve.
Use this first when equipment ratings are mixed between watts, VA, amps, voltage, current draw, or power factor. This creates the load baseline that every later runtime and battery estimate depends on.
Use this after the starting load is known. Growth margin keeps the power plan from being sized only for day-one conditions and shows how future equipment can affect runtime and capacity.
Use this after the load and growth assumptions are understood. Runtime should be treated as a planning estimate that still needs to be compared against manufacturer runtime data before purchase.
Use this after the runtime target is known. Battery bank sizing helps document whether reserve, usable capacity, efficiency, and derating assumptions can support the plan.
These tools support the power plan when the project has extra assumptions to validate. They are useful checks, but they should not be presented as required steps in the main guided design flow.
Use this as a simpler battery estimate when you need an early sizing check before moving into the fuller guided-flow battery bank planning step.
Use this when the power path includes conversion losses. It helps separate input draw from usable output so runtime and battery assumptions are not accidentally too optimistic.
Use this when a battery, module, or string failure could reduce available runtime. It helps show how fragile the plan becomes under a degraded condition.
Use this when redundancy choices change usable runtime or effective capacity. It helps compare resilience assumptions without pretending redundancy is free capacity.
Use this when multiple load, growth, runtime, or efficiency assumptions need to be compared side by side before locking the design direction.
Use this when the plan needs a pessimistic check based on degraded, aged, or otherwise less-than-ideal conditions instead of best-case assumptions.
Use the category workflow, then document the assumptions
After the major assumptions are calculated, review the results as a planning package: starting load, unit conversions, growth margin, runtime target, battery reserve, and runtime and reserve assumptions. Export reports and saved snapshots are most useful when the inputs are clear enough for someone else to understand later.
ScopedLabs tools and guides are planning aids. They do not replace manufacturer runtime charts, electrical code review, project-specific engineering, qualified professional validation, or authority-having-jurisdiction requirements for a final installation.