Commercial Solar-Only vs Solar-Plus-Storage: Which Scope Should You Quote?

For commercial solar vs solar plus storage, the useful question is not “Which technology is better?” It is “Which scope has enough evidence to quote without hiding assumptions?” Start with one common PV design, then compare three controlled cases: PV-only, storage-ready PV, and integrated PV-plus-storage.

PV-only can be the decision-ready base when the current objective is solar production against an operating load and no storage use case is defined. Storage-ready can preserve specific physical or electrical provisions, but only when the quote names what is installed now and what remains uncertain. Integrated storage needs a complete operating, electrical, controls, safety, interconnection, commissioning, and lifecycle scope—not simply a battery capacity beside a price.

No case is the universal winner. The right quote depends on the site’s load timing, current tariff and export rules, resilience objective, critical loads, expected dispatch, available space, electrical architecture, local review, utility process, and ownership horizon. The decision should remain open until those inputs are documented.

Compare three scopes on the same PV base

Require bidders to preserve the same core PV assumptions across the alternatives. Otherwise, the storage decision becomes entangled with a different array size, module count, production model, electrical point of connection, or construction scope.

Scope	What should be complete now	What must not be implied
PV-only	PV design, production assumptions, site/electrical work, monitoring, utility and closeout scope	Outage operation, future battery compatibility, or a specific financial result
Storage-ready PV	Complete PV base plus precisely named pathways, space, electrical provisions, communications, records, and deferred-work list	A future battery can be added without redesign, replacement, new permits, or utility review
Integrated PV-plus-storage	PV base plus battery, power conversion, controls, operating modes, protected loads, site/fire work, commissioning, and lifecycle responsibilities	A stated runtime, demand reduction, savings, utility approval, or resilience outcome

Ask for a separate price schedule for every incremental element. A single combined total makes it difficult to determine whether the difference comes from storage equipment, a changed PV design, switchgear, transformers, protected-load work, controls, civil work, fire-safety measures, utility requirements, software, or contingencies.

The comparison should also retain the same analysis period, rate source, load dataset, PV weather and loss assumptions, escalation assumptions, and operating-change inputs. The commercial solar proposal checklist explains how to normalize whole proposals. This guide owns the narrower decision about which of the three energy-system scopes is supportable.

Decide the operating objective before selecting equipment

A battery can perform different jobs, and those jobs can conflict. Write one primary objective and rank any secondary objectives before asking for capacity or product recommendations.

Possible objectives include:

• shifting energy from one period to another under a verified rate and export structure;
• limiting export when the utility-approved operating mode requires it;
• supporting a defined set of critical loads during selected outage scenarios;
• reserving stored energy for a continuity objective;
• coordinating with an existing generator or UPS under a defined controls sequence;
• preparing the site for a later, separately reviewed storage project; or
• collecting evidence now while postponing the battery decision.

“Reduce the bill,” “add backup,” and “be battery-ready” are not complete objectives. They do not state which measured interval matters, which loads must operate, how much interruption is acceptable, when charging may occur, what reserve must remain, or which authority must accept the configuration.

Use an objective statement that can be tested. For example: “Evaluate an integrated alternate that preserves specified critical processes through owner-defined outage scenarios while maintaining an agreed reserve policy during normal operation.” That statement still does not promise a result. It tells the design and modeling team what evidence to produce.

If the owner cannot yet write the objective, quote PV-only as the stable base and make storage an investigation item. A premature battery size can anchor procurement before the operating problem is understood.

Match load, solar, tariff, and export data on one clock

Annual electricity use is not enough to distinguish the scopes. PV output, facility load, demand intervals, rate periods, exports, battery charging, and battery discharge all occur at particular times. Put them on a common timestamp convention and document the interval length, time zone, daylight-saving treatment, units, missing periods, and meter direction.

Assemble at least:

• current utility bills and the legal utility name;
• rate schedule, riders, contract-demand terms, and export rules from current official sources;
• interval demand and energy data when available;
• operating hours, shifts, shutdowns, seasonal changes, and planned new loads;
• existing solar, battery, generator, UPS, and production data;
• the PV production series used in each case;
• estimated-read, rebill, meter-change, and data-gap flags; and
• the account, meter, building, and service boundary represented by every file.

The commercial solar data guide provides the full input-readiness workflow. Do not fill missing intervals silently or combine meters without documenting the relationship.

Tariffs matter because the same physical energy movement may be valued differently under different schedules. Dominion Energy South Carolina’s current rates and tariffs hub, for example, publishes multiple commercial schedules and riders. That fact supports account-specific review; it does not identify the correct tariff for a site or establish that a storage option qualifies for a particular treatment. Duke Energy Carolinas, Duke Energy Progress, Santee Cooper, cooperatives, and municipal providers have their own current materials and account boundaries.

Record every tariff and export assumption with its source date. Ask the named utility to confirm questions that affect design or operation. Do not generalize one provider’s provision across South Carolina.

Treat dispatch as part of the quoted system

Dispatch is the logic that determines when a battery charges, discharges, holds reserve, stops, or changes mode. It links a physical BESS to the owner’s stated objective.

An integrated quote should explain:

• permitted charging sources;
• whether charging from the grid is contemplated and under what conditions;
• whether export is allowed, constrained, or disabled in the proposed mode;
• the order of priorities among normal bill-related operation, reserve, and other objectives;
• minimum and maximum state-of-charge settings used in the model;
• power, energy, efficiency, temperature, degradation, and availability constraints;
• the meter or control point used for each signal;
• what happens when communications or a sensor fails;
• who may change settings and how changes are logged;
• how existing generation, generators, transfer equipment, or building controls interact; and
• which settings require utility, manufacturer, engineer, or owner review.

NREL’s REopt methodology treats load, rate, technology assumptions, dispatch, critical load, lifecycle, and outage scenarios as site-specific inputs. A key implication is that the same battery can produce different modeled results under different control priorities. A battery used aggressively during normal operation may begin an outage with a different state of charge than one that maintains a reserve.

That is why a capacity figure does not explain performance. Preserve the dispatch narrative, model version, input sources, constraints, and control responsibility with the quote. If a bidder cannot describe how the modeled logic becomes commissioned settings, the result is not yet an operating scope.

Separate demand-charge mechanics from a storage promise

Some commercial rate schedules include demand-related billing components. Storage may change a measured interval if it discharges at the relevant time and the control system responds as assumed. It does not automatically reduce a billed demand value.

The result depends on:

• how the tariff defines the measurement interval;
• which demand component, ratchet, contract term, or time window applies;
• whether the battery has enough available power and energy at the actual peak;
• whether a competing reserve or operating constraint prevents discharge;
• whether the forecast and controls identify the relevant event;
• facility peaks that occur after the battery is depleted or constrained; and
• how the utility applies the current rate to the account.

Use the commercial demand-charge guide for the mechanics and interval-data validation. In the quote comparison, require the bidder to identify the exact tariff field, interval, dispatch rule, constraints, and downside case behind any modeled demand effect. Do not accept a generic “peak shaving” label as evidence.

Define resilience with critical loads and operating states

Ordinary grid-dependent PV generally shuts down when the grid is unavailable. The Department of Energy’s solar and resilience basics explains that outage-capable solar requires an appropriate configuration of inverter, storage, and related system architecture.

Adding a battery line item does not by itself define that architecture. For a resilience objective, inventory the actual loads to be protected:

• equipment name and electrical source;
• operating and starting power;
• energy profile over the outage scenario;
• season, shift, and process dependency;
• acceptable interruption and restart sequence;
• controllable or shed-able status;
• interaction with safety, life-safety, generator, UPS, HVAC, communications, or process systems; and
• evidence owner and current-through date.

Critical load means the subset needed for the owner’s essential services. It is not automatically a percentage of the building’s peak or annual use. A motor, refrigeration system, pump, server, access-control system, or production line may have starting, power-quality, sequencing, environmental, or continuous-operation needs that annual kWh cannot reveal.

Then define the operating states: normal grid-connected operation, transition after grid loss, islanded operation if proposed, restart, solar recharge, low-state-of-charge behavior, load shedding, generator coordination, and grid return. Name the equipment and controls that create isolation and transfer. Identify which loads remain outside the protected boundary.

Runtime cannot be inferred from nominal battery kWh divided by one load number. Available energy, power limits, state of charge at outage start, temperature, degradation, inverter/control behavior, starting loads, changing demand, solar resource, recharge, reserve, and shutdown limits all matter. Model multiple owner-defined scenarios and retain the assumptions; describe them as scenarios, not outcomes.

Make “storage-ready” a written construction scope

Storage-ready is useful only when it describes installed work and controlled assumptions. It is not a product category with one universal meaning.

A defensible storage-ready alternate can identify:

• reserved equipment area and documented clearances;
• structural or civil conditions reviewed now;
• pathways, conduits, trenches, pads, bollards, or access installed now;
• switchgear, panel, transformer, feeder, breaker, and point-of-connection provisions;
• metering, current-transformer locations, communications pathways, and network responsibility;
• control interfaces or gateways installed now;
• PV inverter or power-conversion assumptions, with exact model and documentation where applicable;
• protected-load distribution, transfer, isolation, or generator interfaces installed now;
• drawing, setting, model, permit, utility, and commissioning records preserved at closeout; and
• deferred work, exclusions, allowances, and parties responsible later.

The quote should state how long each assumption remains valid and what must be rechecked. Equipment families change. Loads and rate schedules change. Firmware, listing evidence, codes, utility procedures, available fault current, service capacity, insurance requirements, and owner objectives can change. Even an intentional pathway may need new engineering, permits, utility review, equipment, or construction.

Avoid claims such as “plug in a battery later,” “no redesign,” or “future-proof.” Instead, say exactly what present work may reduce or clarify future work, and list the conditions that can invalidate it. A hybrid inverter alone does not prove that a future battery, controls package, operating mode, or assembled system will be compatible or accepted.

Require an integrated-storage scope, not a battery allowance

An integrated PV-plus-storage alternate should carry a complete installed-system boundary. At minimum, request:

Performance and operating basis

• battery rated power and usable energy at stated conditions;
• allowable operating window, efficiency basis, degradation assumption, and capacity-maintenance approach;
• all modeled operating modes and dispatch priorities;
• charging source, export/nonexport behavior, reserve policy, and critical-load assumptions;
• PV, battery, and load time series used in the analysis; and
• limits on any modeled result.

Electrical and controls scope

• PV inverter, battery power-conversion system, transformers, switchgear, protection, meters, and point of connection;
• AC- or DC-coupled architecture and what that changes in the proposed design;
• transfer/isolation and protected-load distribution if outage operation is proposed;
• energy-management, battery-management, and site-control responsibilities;
• communications, network, cellular, cybersecurity, remote access, data, and credential ownership;
• interface to existing generators, UPS equipment, building controls, and monitoring; and
• controls acceptance tests for every proposed mode.

Site and safety scope

• equipment location, access, drainage, flood exposure, wind, structural/civil work, clearances, and security;
• thermal management, ventilation where applicable, detection/suppression interfaces, signage, emergency access, and responder information;
• exact listing, certification, and test documentation for the assembled configuration;
• permit, plan-review, fire-official, insurer, lender, and owner approval responsibilities; and
• construction phasing, shutdowns, temporary conditions, and restoration.

Commissioning and lifecycle scope

• factory and field tests, functional tests, integrated-system tests, witnessed tests, and acceptance criteria;
• baseline usable-capacity or performance evidence and metering method;
• operator training, emergency procedures, escalation contacts, and spare parts;
• equipment, workmanship, performance, throughput, capacity, controls, and software warranty terms, including exclusions;
• preventive maintenance, remote monitoring, response responsibilities, software subscriptions, firmware, and communications charges;
• degradation review, augmentation or replacement assumptions, disposal/recycling responsibility, and decommissioning; and
• ownership of as-builts, models, settings, test results, credentials, data, and change logs.

DOE’s commercial-scale BESS procurement checklist and customizable lithium-ion BESS specification are useful category frameworks. They are federal resources, not a finished private-project specification or a representation of Sunburst’s service.

Detailed battery cost and procurement analysis belongs in the commercial battery cost guide. For this comparison, the goal is to make every storage delta visible and stop a placeholder allowance from masquerading as an integrated bid.

Verify site, code, fire, and product evidence

Storage can change site planning and the permitting evidence needed for a project. Bring the relevant authority having jurisdiction and fire-review questions into the feasibility stage, not after equipment selection.

South Carolina’s Building Codes Council identifies the statewide code editions and implementation dates. As of August 10, 2026, the implemented family is based on the 2021 building and fire codes and the 2020 National Electrical Code. The Council’s adoption material sets January 1, 2027 for implementation of the adopted 2024 code family and 2023 NEC. A project’s applicable requirements depend on its filing date, location, local modifications, scope, and authority interpretation, so verify the current boundary directly.

Ask for exact equipment and system evidence. UL Solutions describes UL 9540 as a standard covering energy storage systems and equipment, including protection, controls, communications, and grid interaction. It describes UL 9540A as a test method for evaluating thermal-runaway fire propagation. A test report is not the same thing as a system listing, installed-code finding, or project approval.

The design team should map each cited listing, certification, test report, installation instruction, and spacing condition to the exact proposed configuration. Component evidence should not be stretched into a compatibility or approval statement for the assembled system. Record substitutions as change-control events requiring renewed technical, safety, utility, and owner review.

Keep interconnection evidence separate from construction readiness

PV-only, storage-ready, and integrated-storage configurations may not have the same utility review. Storage power, controls, export behavior, point of interconnection, or another design change can affect the application and studies.

The DOE distributed-energy interconnection checklist organizes questions by process step. Apply that discipline to the named South Carolina utility:

1. identify the legal utility and applicable current procedure;
2. document the proposed equipment, capacity, operating mode, export behavior, protection, and point of interconnection;
3. record the application, study, agreements, conditions, and required upgrades;
4. distinguish utility authorization to construct from local permits and owner notice to proceed;
5. preserve inspection, meter, settings, testing, and permission-to-operate evidence; and
6. route every material design or controls change through the required review.

The South Carolina commercial interconnection guide owns that full workflow. Here, the quote must identify which utility submissions and assumptions belong to each scope, who owns them, which fees or upgrades are excluded, and what triggers a revised application. No bidder can predetermine utility approval, upgrade cost, or timing.

Compare lifecycle responsibilities and warranty boundaries

PV and storage may have different owners, installers, monitoring platforms, maintenance providers, warranties, replacement cycles, and change-control rules. An integrated first-day system can still fragment operational responsibility later.

Build a responsibility matrix covering:

Event	Evidence to require
PV alarm or production issue	Monitoring owner, triage path, warranty boundary, response responsibility
Battery or controls alarm	Platform owner, remote-access authority, qualified responder, escalation sequence
Communications failure	Network/data owner, fallback behavior, cost and restoration responsibility
Firmware or settings change	Approval authority, validation test, version log, utility/manufacturer restrictions
Capacity review	Measurement method, test conditions, baseline, warranty threshold and remedy
Equipment substitution	Compatibility, listing, design, permit, utility and warranty re-review
Ownership or service-provider change	Assignment rights, credentials, records and continuing subscriptions
End of contract or useful life	Removal, recycling/disposal, site restoration and data retention

Do not accept “monitoring included” as the whole answer. Identify what is measured, the retention period, data access, alarm routing, platform fees, credential ownership, and who is authorized to change dispatch. Do not assume the PV workmanship warranty covers a later battery retrofit or that a battery provider accepts responsibility for preexisting solar equipment.

These boundaries matter for storage-ready projects too. Closeout records from the PV construction become future design inputs. Require as-built one-lines, equipment schedules, protection settings, conductor/pathway records, structural/civil details, permits, inspection records, utility correspondence, monitoring credentials, test results, and warranty contacts.

Build an incremental bid schedule

Use a three-column schedule rather than three unrelated proposals.

Common PV base

Hold constant the array, production model, electrical base, site assumptions, monitoring, utility boundary, permit assumptions, warranties, closeout, and exclusions. If a storage case changes any PV element, show the change explicitly.

Storage-ready delta

Price each installed-now provision separately. List future work, assumed interface, useful documentation, expiration/reverification conditions, and change triggers. A zero-dollar “ready” label with no construction line items provides little decision evidence.

Integrated-storage delta

Separate battery equipment, power conversion, controls, transfer/isolation, protected-load distribution, transformers/switchgear, civil work, fire/safety work, network/software, utility work, commissioning, training, warranty/O&M, contingencies, and decommissioning assumptions. Identify allowances and exclusions instead of burying them in the total.

Then require a model-assumption table aligned to the price schedule. If the model assumes islanding, export control, a particular reserve, or an equipment capability, the installed scope must show how that function is delivered and tested. If the installed scope includes a function not used in the model, clarify why it is required.

The commercial solar ROI guide owns the year-by-year financial comparison. This page’s contribution is a stable technical and commercial scope that can enter that model without duplicate or missing work.

Use a proceed, investigate, or hold decision

Choose a status for each case instead of forcing a winner.

Proceed as a quote basis

Use this status only when the scope has a defined objective, controlled inputs, a complete equipment and work boundary, stated operating logic, site and utility path, lifecycle responsibility, and explicit unresolved conditions. “Proceed” means the case is ready for the next owner review; it does not mean the project is approved.

Investigate as an alternate

Use this when storage could address a documented objective but critical evidence is missing. Examples include incomplete interval data, an unresolved critical-load inventory, uncertain export treatment, unverified switchgear capacity, a pending fire-review question, or an undefined controls interface. Name the exact evidence, responsible party, and due date.

Hold or remove

Hold a case when the owner has not defined the storage objective, the load is about to change, site control is uncertain, the electrical architecture is undocumented, the proposed mode conflicts with a known constraint, or the bidder cannot support the claimed function. Remove an alternate when it no longer represents the owner’s decision.

A practical request may be: quote the common PV base, provide a fully defined storage-ready alternate if current enabling work is supportable, and develop an integrated alternate only after the critical-load, dispatch, site, and utility gates close. At another site, a current resilience objective may justify evaluating the integrated case immediately. The evidence, not a generic preference, sets the sequence.

Confirm Sunburst’s exact commercial storage scope

Sunburst’s public commercial solar service confirms commercial PV work and mentions pairing solar with batteries, but its published pages do not define a commercial BESS size, voltage, controls architecture, operating-mode range, or delivery geography. Do not infer those capabilities from this guide.

After you assemble the common PV base, interval and tariff records, critical-load inventory, operating objective, site information, and requested alternates, request a commercial solar assessment and ask Sunburst to confirm in writing which PV and commercial-storage assessment, design, procurement, installation, commissioning, monitoring, and lifecycle responsibilities are within its proposed scope. Keep any unsupported function as an owner investigation item.

We quote the three scopes separately on purpose. Sunburst’s commercial solar and battery storage teams price the PV base once, then show storage-ready construction and full solar-plus-storage as priced increments with their own equipment lists, controls, approvals and lifecycle obligations. That makes the resilience or demand-management decision an explicit purchase rather than an assumption buried in a bundle.

For South Carolina facilities the deciding factors are usually the tariff on the account and the cost of an outage to operations. Hurricane-season restoration on the coast is a different resilience case from a brief inland interruption, and we scope them differently. Where the honest answer is that storage should wait, the storage-ready scope is written as buildable construction — conduit, space, capacity, controls — not a marketing label.

Related reading: demand-charge mechanics, commercial battery cost and ROI modeling. Request a commercial assessment or see commercial solar by city.

Questions to put in the quote request

1. What PV design and assumptions remain identical across all alternatives?
2. What primary and secondary operating objectives does the storage case address?
3. Which load, PV, rate, export, and outage inputs drive the model, and what exceptions remain?
4. What charging, dispatch, reserve, export, and failure-state logic is proposed?
5. Which loads are inside and outside any protected-load boundary?
6. What transfer, isolation, controls, and restart/recharge architecture is included?
7. What exactly makes the PV-only case storage-ready, and what future work remains?
8. Which equipment, listings, certifications, test reports, and installation conditions support the exact configuration?
9. Which code editions, local modifications, AHJ, fire review, utility procedure, and filing assumptions apply?
10. What utility application, studies, upgrades, agreements, inspections, meters, and PTO work belong to each case?
11. Which civil, structural, electrical, network, software, commissioning, training, O&M, augmentation, and decommissioning tasks are included?
12. How are PV, battery, controls, workmanship, software, and performance warranty boundaries divided?
13. What data, credentials, models, settings, as-builts, tests, and change logs will the owner receive?
14. What allowances, exclusions, expiration dates, substitutions, and change-order triggers could change the comparison?
15. Which claimed Sunburst commercial-storage services are confirmed in the written scope?

The strongest quote is not the one with the longest benefit list. It is the one that lets an owner trace every objective to a controlled input, design function, installed component, acceptance test, operating responsibility, and unresolved gate.

Frequently asked questions about commercial storage scope

Does adding storage automatically reduce demand charges?

No. A reduction depends on the billing-demand definition in your tariff, the timing and shape of your peaks, the battery’s power and energy limits, the dispatch controls and the state of charge available when each peak occurs. Model it interval by interval against the actual rate schedule before assigning any value to it.

What does “storage-ready” have to include to be meaningful?

A written construction scope: physical space with clearances, conduit and conductor provisions, service and panel capacity, protection and metering arrangements, control and communication pathways, and the interconnection assumptions that would apply. Without those items identified on drawings, the term describes an intention rather than work you have purchased.

Can storage be added later without redoing the solar interconnection?

Sometimes, and sometimes not. Adding storage can change the interconnection review, the equipment listing basis and the operating limits on the account. Ask the utility’s current rules for your specific account and system before assuming a later addition is administrative rather than a new application.

Is resilience the same as demand management?

No. Resilience is about operating defined loads when the grid is unavailable, which requires islanding capability, a defined backed-up boundary and tested transfer. Demand management is a grid-connected economic function. A system designed for one does not necessarily deliver the other, and the equipment and controls differ.

How should we compare a bundled solar-plus-storage price with a PV-only bid?

Insist on the same PV base in both, then treat storage as a priced increment with its own scope. Compare equipment models, usable energy and power, controls and software terms, approvals, commissioning tests and lifecycle obligations. A single bundled number cannot be evaluated against a PV-only bid without that separation.

Sources and methodology

This guide was researched against current public materials on August 10, 2026. Primary methodology sources include:

• U.S. Department of Energy, Solar and Resilience Basics
• U.S. Department of Energy FEMP, Battery Energy Storage System Procurement Checklist
• U.S. Department of Energy FEMP, Lithium-ion Battery Storage Technical Specifications
• U.S. Department of Energy FEMP, Distributed Energy Interconnection Checklist
• National Renewable Energy Laboratory, REopt curriculum and REopt Lite User Manual
• South Carolina Building Codes Council, current code adoption information
• UL Solutions, Energy Storage System Testing and Certification

The DOE and NREL materials are planning frameworks, not project designs. The South Carolina code, utility, rate, interconnection, fire, permit, product, insurance, and contract findings must be confirmed for the actual site and filing date. This article provides a buyer-side scope checklist, not engineering, legal, tax, financial, utility, or code approval advice.