How to use
Separate energy duty from short-duration power capacity
Construct states from synchronized observations or explicit operating modes. Check that shares describe one representative horizon and that surge magnitude, duration, repetition, installed rating, and environmental derating come from compatible evidence.
- Enter idle, typical, and sustained peak power on the same electrical or mechanical boundary.
- Enter relative duty shares from timestamps or justified forecasts; normalization fixes arithmetic totals but not representativeness.
- Set a surge multiplier from measured startup or transient evidence and retain the associated duration and repetition externally.
- Enter installed rating and allowable-loading policy after accounting for ambient, duty class, and manufacturer derating.
- Use weighted average for energy and required nameplate for preliminary capacity, then perform coincidence, transient, and code checks before final sizing.
Operating-envelope fundamentals
Idle state
Lowest sustained powered condition, which may still consume significant energy.
Typical state
Representative operating load, not necessarily a simple midpoint.
Sustained peak
Highest modeled steady operating state.
Surge
Short transient demand requiring capacity but contributing little energy.
Duty-weighted average
Sum of state powers multiplied by normalized time shares.
Result interpretation
Use average power for energy and surge for capacity
Duty-weighted average represents sustained exposure across normalized idle, typical, and peak states. Operating energy extends that average through the entered horizon. Surge and derated required nameplate address short-duration capacity and should not be substituted for average consumption.
Low average power can coexist with a high capacity requirement when peak dwell is short but startup is severe. Negative installed headroom signals that the entered rating is below the simple surge envelope. A load factor near one indicates sustained operation close to peak, while a low value indicates a wider separation between energy and capacity drivers.
Normalize sustained duty before evaluating surge capacity
Duty shares are normalized even when their entries do not total 100. Average power and energy use those shares; surge and derated nameplate are evaluated separately.
Headroom
Installed rating minus surge shows simple instantaneous margin, but not voltage sag or thermal response.
Derating
Required nameplate divides surge by allowable loading, increasing capacity when continuous or environmental limits apply.
State definition
States should be based on logged clusters or operating modes rather than arbitrary percentages of rating.
State construction
Build idle, typical and peak states from observed clusters
Use timestamped loads, operating codes, or known modes rather than arbitrary fractions of nameplate. Each state should have a stable definition, comparable measurement boundary, and enough observations to represent its internal variation.
Separate standby from powered idle when controls or auxiliaries differ, and avoid defining typical as a simple midpoint unless data supports it. If several assets can operate together, construct coincident system states rather than adding independent averages that never occur simultaneously.
Duty normalization
Relative weights are normalized but still need time evidence
The calculator rescales entered shares to 100%, preserving their relative proportions and preventing arithmetic totals from drifting. Normalization does not make guessed shares representative, repair missing states, or establish that the forecast horizon resembles the observed period.
Derive shares from equal-duration records or timestamped dwell time, document exclusions and seasonality, and test alternative profiles when future production changes. If states overlap, use a joint-state or coincident-load model rather than treating their individual shares as mutually exclusive.
Transient capacity
Surge magnitude without duration is only a screening envelope
Generators, batteries, inverters, motors, and power supplies respond differently to transient duration, waveform, repetition, power factor, and the sequence of load steps. One multiplier captures magnitude only and cannot predict voltage dip, frequency response, thermal accumulation, or protective trips.
Retain measured or manufacturer surge duration and repetition externally, then use equipment curves and electrical studies for final sizing. Where several loads may start together, model coincidence and sequencing rather than multiplying only the single sustained peak.
Visual reading guide
Compare state rails with contribution shares
The primary view positions idle, typical, sustained peak, surge, and installed rating on one watt scale. It separates steady states from the transient capacity marker. The supporting view weights only sustained states by normalized duty to show their contributions to average power.
A large peak rail can make a small energy contribution when dwell is low, while a modest idle state can dominate energy when it persists. The visual does not show surge duration, simultaneous assets, or probability, so rail height alone is not a final sizing criterion.
Detailed calculation process
dᵢ = wᵢ/Σw; Pavg = Σ(Pᵢdᵢ); Psurge = Ppeak s; Prequired = Psurge/a
w is entered duty weight, d is normalized share, s is surge multiplier, and a is allowable loading fraction.
| dᵢ | normalized state duty | dimensionless |
| Pavg | duty-weighted power | W |
| Psurge | transient envelope | W |
| Prequired | minimum derated nameplate | W |
Duty check:
Operating evidence
Use synchronized state power and dwell time
Retain timestamped power logs, interval definition, voltage and frequency, asset boundary, state-classification rules, dwell shares, excluded periods, surge magnitude and duration, installed rating, duty class, ambient derating, redundancy policy, and planned operating changes.
Reconcile shares to the represented horizon, average power to integrated logger energy, and installed rating to current manufacturer documentation. Confirm that surge evidence belongs to the same configuration. When forecast states differ from history, label the changed assumptions rather than presenting them as measured facts.
Limits and exclusions
What the simplified envelope omits
The model excludes simultaneous assets, power factor, harmonics, startup waveform and duration, thermal time constants, battery or inverter curves, voltage drop, redundancy logic, protection coordination, code requirements, and probability of coincident peaks. It assumes three non-overlapping sustained states.
Use it for energy-versus-capacity screening, not final electrical design or protection sizing. A detailed load study is required when coincidence, starting behavior, reliability, environmental derating, or governed safety margins can change the nameplate requirement.
Operating-envelope glossary
Terms separating energy from capacity
Idle stateLowest sustained powered condition.
Typical stateRepresentative operating load.
Sustained peakHighest modeled steady state.
SurgeShort transient demand.
Dwell shareFraction of time spent in a state.
Load factorAverage demand divided by peak demand.
DeratingReduction in usable nameplate capacity.
HeadroomInstalled rating above modeled demand.
Worked cases
Two operating envelopes where energy and capacity diverge
Workshop motor supply
Inputs: 0.8/3.6/6.2 kW states, 25/60/15 shares, 1.35 surge, 80% allowable loading and 24 hours.
Calculation: normalize shares for average energy, then calculate surge and required nameplate separately.
Decision: use weighted average for daily energy and the derated surge screen for preliminary capacity.
Idle-heavy edge server
Inputs: idle 0.35 kW, typical 0.70 kW, peak 1.80 kW; shares 70/25/5; surge multiplier 1.6; 3.0 kW installed rating; 80% allowable loading; 24 hours.
Calculation: average power is 0.510 kW and daily energy is 12.24 kWh. Surge is 2.88 kW, leaving only 0.12 kW simple installed headroom, while derated required nameplate is 3.60 kW.
Decision: idle dominates sustained energy, but the 3.0 kW supply fails the derated surge screen. Model redundant-supply failover, coincident loads, surge duration, and manufacturer curves before selection.
Important note
Do not size electrical protection or standby systems from this simplified envelope without load coincidence, code, transient, and manufacturer checks.
Frequently asked questions
Power range questions
Why normalize duty shares?
Normalization rescales the entered weights to 100% while preserving their relative proportions. It corrects arithmetic totals but does not prove the shares represent future operation or that important states are not missing.
Does surge affect energy?
Not in this model because surge has no entered duration. It is used for preliminary capacity screening only. Repeated or long surges can contribute energy and heat and require a time-resolved transient model.
What if typical exceeds peak?
Stop and correct the state definitions or values. Sustained peak should be at least as large as typical on the same boundary; an inversion usually signals mismatched units, periods, or operating modes.
Is rating headroom enough for a generator?
No. Generator selection also needs starting kVA, power factor, voltage dip, frequency recovery, load-step sequence, harmonic loads, ambient derating, and applicable reserve policy. The displayed margin is only a watt-based screen.
Can shares be observation counts?
Yes when every observation represents equal duration and the sample represents the intended horizon. With irregular timestamps, use dwell time rather than counts so short-interval records are not weighted like long intervals.
Why divide surge by allowable loading?
Dividing by a fraction below one converts the usable-capacity policy into a larger minimum nameplate screen. The fraction should come from duty class, environment, reliability, or manufacturer guidance rather than convenience.
Should standby be included?
Include standby as its own sustained state when it consumes power during the modeled horizon. Do not combine it with powered idle if auxiliaries, availability, or control behavior differ materially.
Can this size protection devices?
No. Protection sizing and coordination require fault levels, starting current, conductor characteristics, trip curves, voltage, code rules, and selectivity studies. This page models operating power, not fault behavior.
What if load states overlap?
Use a coincident-load or joint-state model. Adding independent duty shares can create impossible totals or miss simultaneous peaks when several assets and operating modes occur together.