Key Takeaways
- Consumption data can be imported from utility APIs, Green Button CSV/XML files, manual bill entry, or direct smart meter integrations — each with different accuracy and setup trade-offs
- Data granularity ranges from 15-minute interval readings (smart meters) to hourly profiles and monthly billing totals — finer resolution produces more accurate financial projections
- Importing actual usage data enables precise system sizing by matching solar production to the customer’s real demand curve rather than relying on generic assumptions
- Self-consumption modeling requires time-resolved consumption data to determine how much solar energy is used on-site versus exported to the grid throughout the day
- Time-of-use (TOU) savings calculations depend on knowing when the customer uses electricity, not just how much — interval data reveals peak vs. off-peak consumption splits
- Battery storage sizing benefits directly from consumption profile imports because the data shows overnight demand, peak shaving opportunities, and the gap between production and load
What Is Consumption Profile Import?
Consumption profile import is the process of loading a customer’s historical electricity usage data into solar design software so the system can be sized, simulated, and financially modeled against actual demand patterns. Instead of guessing how much electricity a household or business uses, designers import real data that shows when and how much power is consumed throughout the day, week, and year.
The imported data creates a load profile — a time-series representation of electricity demand that the software overlays against projected solar production. This overlay reveals how much energy the system will offset, how much will be exported, and how savings accumulate under the customer’s specific rate structure.
Without consumption data, solar designs rely on assumptions: national averages, rule-of-thumb estimates, or the customer’s rough recollection of their monthly bill. These shortcuts consistently lead to sizing errors. A system designed on assumptions might overproduce in spring (wasting export value under low feed-in tariffs) or underproduce in winter (leaving the customer short during high-rate periods).
Consumption profile import turns a solar proposal from an estimate into a projection. When the software knows that a household draws 2.1 kW at 7 PM every weeknight and 0.4 kW at 2 AM, it can model exactly how a 6.6 kW system with 10 kWh of storage will perform — hour by hour, month by month, dollar by dollar.
Import Methods
Four primary methods exist for getting consumption data into solar design platforms. The right choice depends on what data the customer can provide and what the utility makes available.
Utility API Import
Direct integration with utility data platforms pulls 12–24 months of interval data automatically once the customer authorizes access. No file handling needed. Coverage depends on the utility and region — major U.S. utilities support this through platforms like UtilityAPI and Arcadia.
Green Button Data
The DOE’s Green Button initiative provides a standardized CSV or XML format for electricity usage data. Customers download their Green Button file from their utility’s website and upload it to the solar design tool. Supports 15-minute to hourly interval data depending on the meter.
Manual Bill Entry
The designer enters 12 months of billing totals from the customer’s utility statements. The software then generates a synthetic load profile by distributing monthly kWh across hours using regional load shape templates. Available for every customer but least accurate for TOU and storage analysis.
Smart Meter Integration
Direct connection to the customer’s smart meter or home energy monitor provides near-real-time consumption data at 1-minute to 15-minute intervals. Offers the highest resolution and captures recent changes in usage behavior that historical billing data may miss.
Import Method Comparison
Each import method delivers different data quality, requires different setup effort, and suits different project scenarios. The table below summarizes the trade-offs.
| Import Method | Data Granularity | Setup Time | Accuracy | Best For |
|---|---|---|---|---|
| Utility API | 15-min or hourly | 5–10 minutes | High | Markets with API-enabled utilities; high-volume installers |
| Green Button (CSV/XML) | 15-min or hourly | 10–15 minutes | High | Customers with smart meters; standardized data exchange |
| Manual Bill Entry | Monthly totals | 15–20 minutes | Moderate | Customers without smart meters; quick initial proposals |
| Smart Meter Integration | 1-min to 15-min | 20–30 minutes | Very High | Storage projects; TOU optimization; commercial systems |
For residential projects without TOU rates or battery storage, manual bill entry often provides sufficient accuracy for system sizing. But for any project involving time-of-use rate optimization, demand charge reduction, or battery storage, interval data from utility APIs, Green Button files, or smart meters is worth the extra setup time.
Optimal System Size (kW) = Annual Consumption (kWh) × Offset Target (%) ÷ (Peak Sun Hours × 365 × System Loss Factor)Example: A customer consumes 9,000 kWh/year and wants 90% offset. The location receives 4.5 peak sun hours per day, and system losses (soiling, wiring, inverter efficiency, degradation) total 14%.
Optimal System Size = 9,000 × 0.90 ÷ (4.5 × 365 × 0.86) = 9,000 × 0.90 ÷ 1,412.55 = 5.73 kW
This formula gives a starting point, but consumption profile data refines it. If interval data shows the customer uses 60% of electricity during peak TOU hours, a slightly larger system with battery storage may deliver better financial returns than a system sized purely on annual kWh offset. The generation and financial tool runs these time-resolved calculations automatically when consumption data is imported.
Monthly or even daily consumption totals hide the demand spikes and valleys that determine TOU savings and storage value. A home using 30 kWh/day could draw 1.25 kW steadily — or spike to 8 kW during evening cooking and drop to 0.3 kW overnight. These two patterns produce identical monthly bills but very different solar+storage economics. 15-minute interval data captures these swings, enabling accurate TOU arbitrage calculations and battery dispatch modeling. For any project involving time-of-use rates or storage, insist on interval data before finalizing the design.
Practical Guidance
Consumption profile import affects how accurately you can size systems, model savings, and set customer expectations. The guidance below covers the specific decisions each role faces when working with imported usage data.
- Import at least 12 months of data to capture seasonal variation. A summer-only dataset will miss winter heating loads (or vice versa), leading to a system sized for half the year. Full-year data ensures the design accounts for the highest and lowest consumption months.
- Validate imported data against utility bills before designing. Check that the total kWh in the imported profile matches the customer’s billing statements within 5%. Gaps, duplicate records, or timezone mismatches in interval data can silently skew results.
- Use interval data to identify load-shifting opportunities. If the consumption profile shows a large evening peak, recommend scheduling EV charging, pool pumps, or water heaters to run during solar production hours. This raises self-consumption without increasing system size.
- Overlay the consumption profile on the production curve in your solar design software. The visual gap between production and consumption at each hour tells you exactly how much energy is exported, how much is imported, and where storage fills the gap.
- Confirm that the imported profile reflects current usage before installing. If the data is 6+ months old, ask whether anything has changed — new appliances, EV purchases, occupancy changes, or HVAC upgrades can shift the load profile significantly.
- Install monitoring to track post-installation consumption against the imported profile. Comparing actual performance to the design assumptions validates your work and identifies issues early — before the customer notices a gap between promised and actual savings.
- Use consumption data to set realistic battery backup expectations. Show the customer their overnight consumption from the imported profile, then explain how many hours the battery will cover at that draw rate. Concrete numbers prevent misunderstandings.
- Flag anomalies in the imported data during the site visit. If the data shows unusually high base loads, check for phantom loads or outdated equipment on-site. Fixing these before installation improves system performance and customer satisfaction.
- Request utility login credentials or Green Button data at the first customer interaction. The earlier you get consumption data, the faster you can deliver an accurate proposal. Make it part of your standard intake process.
- Show customers how their actual usage shapes the proposal. Walking through their consumption profile builds trust because the customer sees their own data driving the numbers — not generic estimates or optimistic assumptions.
- Use TOU consumption splits to sell battery storage. If interval data shows 40%+ of consumption falls during peak rate hours, the savings from shifting that demand to stored solar energy make a compelling financial case for adding a battery.
- Compare proposals with and without imported data. If a competitor delivers a generic estimate and you deliver a proposal built on the customer’s actual usage, the difference in credibility is immediate. Use the generation and financial tool to generate detailed savings breakdowns tied to real consumption patterns.
Import Customer Usage Data for Precise System Sizing
SurgePV imports utility interval data, Green Button files, and manual bill entries directly into the design workflow — so every system size, savings estimate, and storage recommendation is grounded in the customer’s actual consumption.
Book a DemoNo commitment required · 20 minutes · Live project walkthrough
Sources & Further Reading
The following resources provide standards, data formats, and research related to consumption profile import and load analysis for solar design:
- NREL — End-Use Load Profiles for the U.S. Building Stock
- U.S. DOE — Green Button Initiative
- EIA — Residential Energy Consumption Survey (RECS)
Frequently Asked Questions
How do you import electricity usage for solar design?
The most common methods are utility API integration, Green Button file upload, and manual bill entry. With a utility API, the customer authorizes data access and the solar design platform pulls 12–24 months of interval data automatically. Green Button is a standardized CSV or XML format that customers download from their utility’s website and upload to the design tool. For customers without smart meters, designers enter monthly billing totals from 12 months of utility statements, and the software generates a synthetic hourly profile using regional load shape templates.
What is Green Button data?
Green Button is a U.S. Department of Energy initiative that standardizes how utilities share electricity usage data with customers. It provides consumption data in a machine-readable XML or CSV format that solar design software can import directly. The data typically includes 15-minute or hourly interval readings covering 12–24 months of history. Over 150 U.S. utilities and electricity suppliers support Green Button, making it one of the most widely available sources of detailed consumption data for solar designers.
Why does consumption data matter for solar sizing?
Consumption data determines the right system size, the expected savings, and whether battery storage makes financial sense. Without it, designers rely on averages that can miss the customer’s actual usage pattern by 20–30%. A household that uses most of its electricity in the evening (after solar production drops) needs a different system configuration than one with high daytime loads. Imported consumption profiles let the software model self-consumption rates, calculate TOU savings accurately, size storage to cover real overnight demand, and produce financial projections the customer can trust.
About the Contributors
CEO & Co-Founder · SurgePV
Keyur Rakholiya is CEO & Co-Founder of SurgePV and Founder of Heaven Green Energy Limited, where he has delivered over 1 GW of solar projects across commercial, utility, and rooftop sectors in India. With 10+ years in the solar industry, he has managed 800+ project deliveries, evaluated 20+ solar design platforms firsthand, and led engineering teams of 50+ people.
Content Head · SurgePV
Rainer Neumann is Content Head at SurgePV and a solar PV engineer with 10+ years of experience designing commercial and utility-scale systems across Europe and MENA. He has delivered 500+ installations, tested 15+ solar design software platforms firsthand, and specialises in shading analysis, string sizing, and international electrical code compliance.