Quick answer
An estimate of a building’s underlying recurring electricity demand using stated data, operating conditions and a defined method. A monthly average or one observed minimum is not proof of a constant load, and total interval demand remains necessary for solar and storage analysis.
Answer: Base load estimation identifies the underlying recurring demand in a building’s electricity profile. It can help describe low-activity consumption, but the result depends on the measurement boundary, time resolution, season and chosen method. A monthly average is not a continuous minimum, and one low reading is not necessarily representative. Solar self-consumption and backup sizing need the relevant full load profile, not one base-load number alone.
Decide what the estimate should represent
In a building context, “base load” can refer to a low-activity demand level, recurring equipment consumption or an estimate of non-weather-sensitive energy use. State the intended meaning rather than treating these as the same measurement.
Refrigeration, networking, security and other equipment may contribute, but some cycle or change operating modes. Occupancy, season, shutdowns and control schedules can change the apparent floor. A building need not draw the same nonzero power at every instant.
Choose evidence appropriate to the task
| Evidence | Useful contribution | Limitation |
|---|---|---|
| Measured interval data | Shows time-dependent demand and low-activity periods | Needs units, timestamps, boundary and data-quality checks |
| Monthly bills | Establishes billed energy and longer-term changes | Does not reveal the demand floor or load coincidence |
| Equipment inventory | Provides a scenario where measurements are absent | Nameplate demand and assumed runtime may differ from actual use |
| Representative modeled profile | Supports preliminary analysis and sensitivities | Is not a measurement of the customer’s building |
NLR’s End-Use Load Profiles project explicitly describes its profiles as simulated building-model outputs calibrated and validated against empirical datasets. They are useful reference profiles, not proof of the actual site’s minimum load. NLR end-use load profiles.
The REopt load-input tutorial distinguishes representative simulations from uploaded site interval data and highlights calendar alignment. These are REopt instructions, not a claim about SurgePV import capabilities. REopt load-profile tutorial.
Clean and interpret the data first
Confirm whether readings are interval energy in kWh, interval-average demand in kW, cumulative readings or another quantity. Match time zones, daylight-saving changes, interval boundaries and the meter’s coverage. Flag missing readings, duplicates, outages and changes in equipment operation.
A meter measuring net grid import at a solar site does not necessarily show the building’s gross consumption. PV output, battery flows and the relevant measurement boundaries may need reconciliation before estimating the underlying load.
Hypothetical unit check: an interval contains 0.25 kWh over 15 minutes. Its average demand is 0.25 ÷ 0.25 hours = 1 kW. This is an interval average, not a measured instantaneous minimum.
Use a defined low-activity method
Select relevant low-activity periods and inspect their distributions across representative days and seasons. A daily minimum, median within a quiet window or another statistic can summarize the data, but each answers a different question. Document the rule, exclusions and variation rather than labeling a statistic “the true always-on load.”
Averaging daily minima does not automatically remove the effect of outages, missing values or unusual shutdowns. Investigate those events before deciding whether they belong in the estimate. There is no universal three-month sample that guarantees a reliable result for every site.
A bill average is not a floor
Hypothetical bill example: 540 kWh over exactly 30 days gives 540 ÷ (30 × 24) = 0.75 kW average demand. It does not demonstrate that the building always draws at least 0.75 kW; its load may be lower overnight and higher during occupied periods.
Sensitivity example: a uniform 0.3 kW difference sustained for a non-leap year represents 0.3 × 8,760 = 2,628 kWh. That quantifies assumed energy variation, not automatically misallocated solar self-consumption. Solar production overlaps only particular times and must be compared interval by interval.
Apply the result without overextending it
For behind-the-meter PV without storage, self-consumption depends on coincident total load and generation. A single midday base/production ratio is not an annual self-consumption rate. Scheduled EV charging is a scenario-specific load, not necessarily an always-on floor.
For backup, define the supported critical loads, their duration and startup requirements. A hypothetical constant 1 kW AC load for 10 hours requires 10 kWh delivered AC energy before considering how storage and conversion deliver it. This does not specify battery nameplate capacity, reserve settings or approved backup equipment. See battery storage for those distinctions.
Designers should retain a current-load scenario and separate future-load assumptions. Qualified monitoring and commissioning teams should follow the approved equipment and safety procedures; one clamp-current reading alone does not establish representative real power. Sales teams should explain uncertainty rather than promise that a base-load estimate keeps every appliance operating through any outage.
See load profile analysis and load analysis for the broader workflow. To evaluate available outputs, book a SurgePV demo with your data format and intended comparison.
Frequently asked questions
Can monthly energy identify the minimum load?
No. Dividing energy by elapsed hours gives average demand, not a continuous minimum.
Is a daily minimum enough for solar savings?
No. Use the coincident load and generation profile with the actual tariff and accounting boundary.
Are modeled reference profiles customer measurements?
No. Label them as modeled scenarios and explain their limitations.
Does base load alone determine battery size?
No. Supported loads, duration, power limits, conversion losses, reserve and the approved backup configuration also matter.
Related Glossary Terms
About the Contributors
CEO & Co-Founder · SurgePV
Keyur Rakholiya is identified by SurgePV as its CEO and a company co-founder. His SurgePV author page lists only role information that can be tied to the public profile below; credentials, project totals, testing claims, media appearances, and speaking engagements are not asserted without retained evidence.
Editorial contributor · SurgePV
Rainer Neumann is credited as an editorial contributor on SurgePV content. This profile does not assert engineering credentials, project totals, software-testing experience, education, speaking engagements, or media citations because independent verification evidence is not retained in the publication record.
