Designing for the peak, not the average: MENA solar and storage

Renewable capacity across the Middle East and North Africa (MENA) grew from 30.3 GW to 43.7 GW in a single year. Solar photovoltaic (PV) accounts for 34.5 GW, wind for 7.4 GW, and concentrated solar power (CSP) for 1.8 GW. Saudi Arabia has crossed 11 GW of operational solar, the UAE has passed 6.5 GW, and Oman reached 1.6 GW after Manah I and II came online.

Those numbers tell you how much is being built, but they don't highlight the bigger challenge.

Building solar in MENA is not just a capacity challenge; it's a timing challenge. Electricity demand spikes in the late afternoon and evening, when air conditioning loads peak, and solar generation is already falling. Those windows are short and predictable, and they're where almost all the revenue is. A system that generates well at noon, in most MENA pricing structures, leaves significant value on the table. Getting solar and storage design right in MENA means understanding not just how much the system generates, but when.

What MENA's storage pipeline is telling you

Battery energy storage system (BESS) deployment in MENA reached 25 GWh of operational capacity in 2025, with a pipeline heading toward 156 GWh. Batteries already account for roughly half of installed storage capacity. Two things are driving that: PV component costs keep falling, and grid operators are increasingly requiring projects to include dispatchable capacity. Unlike pumped hydro or thermal storage, batteries ramp up and down within seconds, which matters when you're managing a steep evening demand curve.

The direction is clear. Standalone solar is giving way to hybrid. But a hybrid system that doesn't account for when demand peaks, and at what price, can still underperform. More storage capacity doesn't automatically mean more value. How you dispatch it does.

The problem with hourly data in a high-irradiance market

Most performance modeling relies on hourly irradiance data. Within any given hour, irradiance can spike well above average and drop back. Those spikes are where inverters get pushed past their limits, and clipping losses occur. Average that hour into a single number, and the spike disappears entirely. Your model shows clean generation; however, the real system could be clipping, and you have no visibility into when or why.

In MENA, where irradiance is consistently high and intra-hour variability is significant, hourly averages understate losses, affecting yield projections and, eventually, lender confidence. RatedPower's sub-hourly modeling captures this variability directly. You can see when production exceeds inverter capacity, how often short-duration spikes occur, and how those events accumulate across a full year of simulated operation. That changes how you approach the decision on the DC-to-AC ratio.

Sizing DC-to-AC when the tradeoff isn't obvious

In a high-irradiance market, the DC-to-AC ratio isn't a fixed calculation. It's a tradeoff you need to test against actual system behavior.

Increasing DC capacity relative to inverter capacity can deliver more energy or more clipping losses, depending on when irradiance peaks hit relative to your inverter limits. Hourly data makes that trade-off look different from what it is, because it flattens the moments when the decision has the greatest consequences. With sub-hourly resolution in RatedPower, you can test inverter sizing against site-specific irradiance profiles, compare configurations based on observed behavior, and see exactly how much energy each scenario clips and when it occurs.

For projects going through lender technical review, this matters directly. An independent engineer may ask whether your clipping loss assumptions are based on hourly or sub-hourly data. The answer affects how much weight they give to your P50 yield figure.

Choosing between hybrid and PV only on revenue, not output

In a market with flat or near-flat pricing, total annual output is a reasonable proxy for project value. In MENA, this isn’t always the case.

Evening peak prices run materially higher than midday prices. A PV plant generates most of its energy between 9am and 3pm, well before the peak. A hybrid can shift stored energy into the evening window, but the value of that depends on how precisely you can time the dispatch. Comparing configurations on total output misses the point entirely.

RatedPower lets you upload time-based energy prices and run production simulations at sub-hourly resolution. Instead of comparing annual totals, you can see how much energy each configuration allocates to high- and low-priced windows and what that means for modeled revenue. That's the comparison that holds up in front of a financing committee.

Keeping inputs consistent from concept to close

There's a failure mode that shows up regularly in project finance: the numbers in the financial model don't trace back to the inputs used in design. Assumptions drift between stages. The engineering team uses one irradiance dataset; the financial model pulls from another. A degradation rate gets adjusted in a spreadsheet without updating the performance simulation. By the time the project reaches an independent engineer, the documentation trail has broken down.

Lenders in MENA know this problem. They ask specific questions about where yield figures come from and whether the input set is consistent from feasibility through close.

RatedPower runs performance simulations and designs from the same set of inputs, with a temporal resolution that reflects how the system actually behaves under changing irradiance conditions. The result is bankable solar design documentation that is consistent with construction, which makes it defensible at financial close rather than something you have to retrofit justifications for.

Getting the dispatch strategy into the design process early

In a market where revenue compresses into a short peak window each day, dispatch strategy isn't something you finalize after the design is done. Battery sizing, inverter capacity, DC-to-AC ratio, and charge and discharge timing all interact. Getting those interactions wrong at the design stage is expensive to correct later, and even more expensive to explain to lenders.