RESOLV Intelligence / Economics

24 June 2026 / 7 min read

The load profile is the project

Why an average consumption figure is the most expensive assumption in industrial energy planning.

Two factories each consume 400,000 units a month. One runs a single shift with a strong midday peak. The other runs continuously with a night-heavy profile. A system sized on the monthly total will be oversized for the first and badly matched for the second. The monthly total is not a design input.

Three shapes that decide three different systems

• /Daytime-heavy load: solar generation lands inside the consumption window and offsets metered units directly. Storage adds little.
• /Flat round-the-clock load: solar covers a slice of the day and the remainder is bought at night. Storage becomes the mechanism that moves generation into the dark hours.
• /Seasonal load: the crushing or processing season concentrates the year into a few months. A system sized for the annual average will be idle for most of it and short during the period that matters.

What measurement costs versus what assumption costs

Installing interval metering for a full operating cycle costs a fraction of the capital being considered. It also produces the single most useful document in the project: a load profile with the peak, the shape and the seasonality visible on one page. Every subsequent engineering decision references it, and every reviewer can be shown the evidence behind the sizing.

The diesel question

Where a generator runs, its hours are a load profile in disguise. A generator that runs for load-following rather than for backup is expensive generation, and the correct intervention may be storage or hybrid control rather than more panels. Capturing generator start hours alongside grid consumption is what makes that visible.

RESOLV's energy assessment begins with measurement. The output is a preliminary project profile: the facility, its energy environment, the recommended evaluation and the next step. No savings figure is promised before the load data exists, because a promise made on an average is a promise that the plant will have to pay for.