Ir al contenido

Off-Grid Resort BESS Sizing: Daily Loads, Autonomy and Recharge

17 de noviembre de 2026 por
Off-Grid Resort BESS Sizing: Daily Loads, Autonomy and Recharge
Hugo Zhang

Consider an off-grid resort whose owner wants to keep the lights on, the cold rooms cold and selected guest rooms cool through two days of poor solar production, with the diesel generator staying off the whole time. The resort must then rebuild its battery reserve while remaining open.

“How many kilowatt-hours per day, and how many days of battery?” starts the discussion. It leaves several decisions open: how much electricity is needed after sunset, what generation can be counted on, what must start together, and when the battery must be ready again.

So let’s work through those decisions in order. We’ll follow a single load schedule through a 48-hour low-solar event and the 24-hour recovery window after it, then turn the results into requirements for a stationary cabinet or containerized BESS.

Set the resort’s service requirements before sizing storage

The site is a three-phase commercial installation supplied by PV, battery storage and an available diesel generator. There is no routine utility supply or grid charging.

The agreed services cover communications and controls, refrigeration, public lighting, selected guest-room cooling, water pumping and laundry/service equipment. Other resort facilities sit outside this calculation. The operations team must identify the actual circuits covered before anyone describes the proposal as “resort backup”.

Write the operating requirement into the project brief:

  • Maintain these services for 48 hours of low solar production, starting at 06:00. Do not credit generator output during those two days.
  • Continue supplying the same loads during the next 24 hours, and restore the battery to its agreed starting state by 06:00 the following morning.
  • Compare PV-only recovery with a second option that permits generator operation from 20:00 to 06:00.

That last permission matters at a guest property. If night-time generator operation is unacceptable, the second option cannot be used to approve the design.

Assumed design inputs: The loads, generation profiles and battery settings below are inputs for this worked example. On a live project, the facilities team supplies the operating schedule, the EPC establishes the solar resource, and the equipment supplier confirms the usable capabilities. Keep those responsibilities visible as the calculation develops.

Build a daily load schedule that preserves when power is used

Start with the equipment the resort has agreed to keep running. Record running power, operating windows and cycling behaviour together.

Load groupEnergy calculationOperating windowDaily AC energy
Communications and controls0.5 kW × 24 hContinuous12 kWh
Refrigeration6 kW running × 8 equivalent hoursCycles throughout the day48 kWh
Public lighting3 kW × 12 h18:00–06:0036 kWh
Selected guest-room cooling20 kW running × 60% duty × 12 h18:00–06:00144 kWh
Water pump7.5 kW × 4 h10:00–14:0030 kWh
Laundry/service equipment6 kW × 3 h11:00–14:0018 kWh
Agreed service loads288 kWh
BESS auxiliariesAssumed constant 1 kW × 24 hContinuous24 kWh
Total model demand312 kWh/day

The refrigeration entry means eight equivalent running hours spread across the day. It does not mean the compressors run continuously for one convenient eight-hour block. For the hourly energy calculation, refrigeration averages 2 kW, while the selected cooling group averages 12 kW during its operating window. Their full running powers remain relevant to the separate power conversion system (PCS) check.

Splitting the schedule at 06:00 and 18:00 reveals the storage task:

06:00–18:00: 90 kWh. 18:00–06:00: 222 kWh, including auxiliaries.

Most demand falls after solar production ends. Two resorts with the same daily energy consumption could therefore need different storage if one uses more electricity during daylight.

Ask facilities staff to check the dependencies behind the table. Does the water system need another pump or treatment stage? Does refrigeration include every cold room promised in the service scope? Missing supporting equipment understates both daily consumption and power demand. Keep estimates identified until operating records replace them.

NREL’s off-grid system modelling guidance uses hourly electricity demand based on equipment, timing of use or metered data. The schedule above provides that starting point; a monthly bill or a room count cannot show this overnight requirement.

Separate no-charge autonomy from low-solar operation

Before calculating “two days”, decide what the battery is expected to do during them.

No-charge autonomy means the battery alone supplies the agreed loads, with no PV or generator contribution. Low-solar operation allows the specified PV production to serve loads and charge storage when a surplus exists. These are different tasks.

PVsyst’s autonomy definition assumes no solar input and a fully charged starting battery. Here, both comparisons deliberately start at 60% state of charge (SOC). That condition must accompany the result: a battery that could pass from full charge may fail from its normal operating state.

For this example, the normal/recovery-day PV profile supplies 460 kWh at the AC bus. The one-hour average outputs, from 06:00 through the interval starting at 17:00, are:

Hour starting06:0007:0008:0009:0010:0011:0012:0013:0014:0015:0016:0017:00
Average output (kW)4102445657575654528159

Output is zero in the remaining hours. Low-solar day one uses 20% of that profile, giving 92 kWh; day two uses 30%, giving 138 kWh. These factors describe the test sequence, rather than a weather recommendation for another location. An actual project needs local seasonal generation data, because 460 kWh/day alone can’t tell you the PV array’s required kWp.

The battery calculation uses the following common settings:

SettingValue used
Capacity basisInitial nominal DC energy; checked at 80% capacity retention
Starting and recovery-target SOC60% of retained capacity
Lower stop / upper charging limit10% / 90% SOC
Discharge-path / charge-path efficiency95% each, applied separately
AC discharge / charge power limit40 kW each, assumed for the energy model
Time step and reporting pointOne hour; each day runs 06:00 to next 06:00

The 80% retention point is a design assumption. It isn’t tied to a particular year or warranty claim. The efficiencies are one-way values. PV output is already measured after PV inversion, and BESS auxiliaries are already counted in demand, so neither needs another deduction.

Work through the energy deficit before selecting a battery candidate

Calculate each hour in operating order. PV supplies the AC loads first. Any surplus charges the battery within its power and SOC limits; any shortfall is supplied through the discharge path. Carry the remaining stored energy into the next hour, checking the lowest point along the way.

For this sequence, battery-side stored energy falls by at most approximately 421.72 kWh over the first 48 hours. Simply subtracting the two days’ PV from their load misses the separate charging and discharging losses.

Only the energy between the 60% start and the 10% lower stop is available for this task. Although charging may reach 90%, the event begins at 60%, leaving a 50-percentage-point discharge window:

Minimum initial nominal DC capacity = 421.72 ÷ [0.80 × (0.60 − 0.10)] ≈ 1,054 kWh.

Carry a 1,100 kWh, or 1.10 MWh, nominal DC candidate into the remaining checks. At the assumed 80% retention point, it has 880 kWh of capacity. Starting stored energy is 528 kWh; the 10% lower stop is 88 kWh; and the 90% charging limit is 792 kWh. The task can therefore consume 440 kWh of stored energy from its starting state.

No additional protected reserve has been specified. If the owner requires one, define that requirement explicitly and recalculate. Don’t add another percentage with the same purpose as an existing limit.

The stage results are shown together below so the recovery checks can use the same candidate and starting point. Every stage lasts 24 hours.

StagePV AC energyGenerator AC energyDemandEnding stored energyEnding SOC
Start, 06:00———528.00 kWh60.0%
Low-solar day 192 kWh0312 kWh294.74 kWh33.5%
Low-solar day 2138 kWh0312 kWh106.28 kWh12.1%
Following recovery day: PV only460 kWh0312 kWh166.15 kWh18.9%
Alternative same recovery day: PV + generator460 kWh400 kWh312 kWh565.14 kWh64.2%

The last two rows are alternative recovery branches. Both start at 106.28 kWh; they are not consecutive days.

The candidate gets through the two-day low-solar event without unmet demand in this simplified model. Its minimum stored energy is 106.28 kWh, just 18.28 kWh above the lower stop. It passes, but narrowly: that’s a sliver of margin, not another operating day.

Now apply the no-charge autonomy condition to the same loads and battery settings. The battery must deliver 312 × 2 = 624 kWh AC without any generation:

Required nominal DC capacity = 624 ÷ [0.95 × 0.80 × (0.60 − 0.10)] ≈ 1,642 kWh.

The 1,100 kWh candidate can deliver only 440 × 0.95 = 418 kWh AC from that starting window. It therefore fails the two-day no-charge requirement, even though it passes the specified low-solar sequence. Same battery, same loads, two answers: the difference is whether any PV is allowed to help.

These are energy results for the stated inputs, so the figures set a candidate requirement, not a purchase configuration. Equipment availability is assumed, and temperature and altitude derating, equipment outages and actual efficiency curves still need project checks. For the underlying energy and SOC method in a shorter outage task, see the two-hour commercial backup sizing guide.

Check PCS power against simultaneous loads and equipment starts

The PCS must support the equipment combination that can actually run together. Daily energy and hourly averages can’t show whether it does.

At night, the running-load check is:

20 kW cooling + 6 kW refrigeration + 3 kW lighting + 0.5 kW communications + 1 kW auxiliaries = 30.5 kW.

During the daytime pump-and-laundry window, the equivalent combination is 21 kW. Adding every device in the table would overstate the planned simultaneous load, while using the 18.5 kW overnight energy average would understate the running combination.

Using an assumed aggregate power factor of 0.9, the 30.5 kW night load corresponds to:

30.5 ÷ 0.9 ≈ 33.9 kVA.

Request both islanded kW and kVA capability from the supplier. The energy model’s 40 kW discharge limit does not establish the PCS’s apparent-power capability, overload duration or ability to start motors.

For the pump, refrigeration compressors and cooling equipment, collect starting method, starting current or power, duration and permitted sequence. Establish what can restart together after a shutdown, as well as what normally runs together. Staggered starts may help, but the control arrangement must enforce them.

The supplier and EPC must also confirm battery DC output at low SOC, phase loading and relevant environmental derating. On top of that, they must confirm the system’s ability to establish and regulate the off-grid supply. Check how its own controls and auxiliaries receive power during start-up. A generic “add 20% to inverter size” allowance cannot settle those questions.

Check whether the resort can recharge while it stays open

At 06:00 after the second low-solar day, the candidate holds 106.28 kWh. The agreed recovery target is 528 kWh, or 60% SOC, by 06:00 the next morning. The resort continues using 312 kWh during that window.

PV-only recovery falls short

The recovery-day PV total is 460 kWh. Subtracting demand gives an apparent surplus of 148 kWh, but that is not the battery’s stored-energy gain.

Midday surplus sometimes exceeds the assumed 40 kW charging limit. About 61 kWh cannot be used by the loads or accepted into storage. This example assumes that output can be curtailed; the actual PV and BESS controls must support that behaviour.

Across the day, 309 kWh AC enters the charging path. The following night then requires 222 kWh AC from the battery:

Net stored-energy recovery = 309 × 0.95 − 222 ÷ 0.95 ≈ 59.87 kWh.

The battery ends at 166.15 kWh, or 18.9% SOC. It has gained energy, but at 18.9% against a 60% target it is nowhere near ready. The next low-solar event would start from a much weaker position.

Compare recovery at the same clock time. A reassuring SOC at sunset excludes the overnight consumption that this resort still has to supply.

Permitted generator operation changes the result

Return to the same 106.28 kWh starting point. Keep the PV and loads unchanged, and allow the generator to provide 40 kW at the AC bus from 20:00 to 06:00.

That contributes 400 kWh, but the running resort receives its share first. The energy-average load during those ten hours is 18.5 kW, leaving an average 21.5 kW for the AC charging path:

400 kWh generator output − 185 kWh direct load supply = 215 kWh entering the charging path.

Charging losses still apply. Combined with daytime PV recovery, this branch ends at 565.14 kWh, or 64.2% SOC, exceeding the 60% target under the stated assumptions. With the night-time generator allowed, the battery is back above its target by 06:00.

This branch depends on acceptable night-time operation, available fuel and equipment compatibility. The 40 kW is simply the AC output we assume is available. It isn’t a generator sizing recommendation. Actual compressor cycling changes instantaneous charging headroom; source controls and charge limits must handle that variation. If noise restrictions remove the operating window, the recovery check must be rerun.

Compare changes to storage, solar, generation and the service requirement

The calculation gives the owner and EPC a specific decision: the candidate gets through the low-solar event, but the PV-only branch misses the next-day recovery target.

Possible changeWhat it can addressWhat to check before accepting it
Add battery capacityMore stored energy available for the eventRecovery energy still has to come from a source; compare options on the same service and the same level of readiness
Increase usable PV contributionMore direct supply or charging opportunitySeasonal timing, low-solar output, charging limits and curtailment
Permit generator assistanceSupply loads while leaving charging headroomAccepted hours, available output, fuel and integration; the tested night-time branch reaches 64.2% SOC
Reduce or defer loadsLower or shift the demand the system must serveOwner approval of the changed service, followed by recalculation

A larger battery does not create recharge energy. Likewise, adding PV capacity may produce more midday surplus than the charger can accept. Review generation and charging capability together.

GSES’s study of PV capacity and battery autonomy illustrates why weather, generation and storage should be assessed together. It does not provide a universal oversizing factor for this resort.

Keep comparisons tied to the same agreed services. Turning off guest-room cooling to make a proposal pass changes the agreement. Comparing identical SOC percentages across different battery capacities can also mislead: agree how much usable energy the next event needs, then check whether each option can get it back in the time available.

Turn the result into a cabinet or container BESS configuration brief

The output is now detailed enough for equipment discussions, while keeping unconfirmed items visible.

RequirementCurrent basis or resultStatus and next responsibility
Service scope and load schedule288 kWh services + 24 kWh auxiliaries; specified operating windowsAssumed — operations/facilities to confirm circuits, duty cycles and supporting loads
Low-solar supply task48 h; PV contributions of 92 and 138 kWh; no generator creditAssumed — EPC to replace the solar profile with site evidence; owner to approve the task
Battery energy candidate1,100 kWh nominal DC at 80% retention; 60% start, 10% stopCalculated from assumptions — supplier/EPC to verify against equipment and site conditions
PCS requirement30.5 kW simultaneous running load; approximately 33.9 kVA at assumed power factorStarts and actual capability unknown — facilities, supplier and EPC to resolve
Recovery requirementReturn to 60% within 24 h while operating; PV-only fails, specified generator branch passes the energy checkConditional — owner to approve generator hours; EPC/supplier to verify charging and sources
Interfaces and site arrangementPV regulation, generator controls, protection, start-up supply and installation arrangementUnknown — local EPC to coordinate with equipment suppliers

Both cabinet BESS and containerized BESS can enter the configuration assessment. The 1.10 MWh candidate is only the starting point for the enclosure, unit count and PCS arrangement. Check equipment included, supported parallel operation and distribution distances. Then add maintenance access, delivery constraints and expansion needs. The cabinet-versus-container comparison supports that next discussion. The BESS project requirements checklist helps organise the wider site information.

Bring the load schedule, PV basis, generator restrictions, recovery deadline and clearly marked unknowns to a GeePower commercial ESS project discussion. We can support product configuration and engineering information alongside the local EPC, which develops the site design and integration. Then the next proposal has a clear job to do, and every open question has someone’s name against it.


Got a load schedule and a recharge deadline?

Bring your load schedule with operating times, your PV basis, any generator restrictions, the recharge deadline and a list of what’s still unknown. We can support product configuration and engineering information alongside your local EPC, who develops the site design and integration.

FAQ

It depends on when the resort uses power, not just how much. In our worked example, the agreed services use 312 kWh a day, and 222 kWh of that falls between 18:00 and 06:00, when there’s no solar. Getting through a 48-hour low-solar event from a 60% start needed at least about 1,054 kWh of nominal DC capacity, so we carried a 1,100 kWh candidate forward. These figures come from assumed inputs, so don’t copy them to another site.

No-charge autonomy means the battery alone supplies the loads, with no PV and no generator. Low-solar operation lets reduced PV serve the loads and charge the battery when there’s a surplus. They’re different tests. In the example, the 1,100 kWh candidate passes the 48-hour low-solar sequence but fails two days of no-charge autonomy, which would need about 1,642 kWh of nominal DC capacity.

It can, but the source matters. In the example, a PV-only recovery day left the battery at 18.9% SOC against a 60% target. Allowing a generator to supply 40 kW at the AC bus from 20:00 to 06:00 brought it to 64.2%. That only works if night-time generator operation is acceptable at the property. A larger battery doesn’t add recharge energy on its own.

By what runs at the same time and what has to start, not by daily energy. In the example, the night-time running load is 30.5 kW, or about 33.9 kVA at an assumed power factor of 0.9. Ask the supplier for islanded kW and kVA capability, overload duration and motor-starting ability. A generic “add 20%” allowance can’t answer those questions.

The energy result alone doesn’t decide it. Enclosure type, unit count and PCS arrangement also depend on what each option includes, supported parallel operation, distribution distances, maintenance access, delivery constraints and expansion plans. Both can enter the assessment. Our cabinet-versus-container comparison is a good next read.

References / Sources

  1. NREL — Designing and Modeling Off-Grid Solar Systems. Method reference for hourly demand, equipment timing and combined source modelling. Official PDF.
  2. PVsyst — Autonomy and battery sizing (stand-alone). Definition and starting-state context for battery-only autonomy. Documentation.