Quick answer
The amount of distributed generation that a grid area can accommodate under stated study conditions before changes or upgrades are required; a screening result rather than project approval.
Answer: Hosting capacity is the amount of distributed generation a grid area can accommodate under stated study conditions before changes or upgrades are needed. It depends on location, network equipment, loads, existing resources and operating assumptions. Published hosting-capacity data can support site screening, but it does not reserve capacity or replace a project-specific interconnection review.
A conditional study result, not a universal feeder limit
Hosting-capacity analysis tests a network model against defined criteria. Voltage, thermal loading, protection and power-quality constraints can matter, but which binds depends on the network and study. Capacity is not reliably calculated by subtracting existing PV from a transformer or feeder nameplate rating: loads, topology, connection location and operating behavior also matter.
NLR’s hosting-capacity explanation describes capacity as dependent on equipment, DER location/behavior and utility planning practices. It distinguishes snapshot studies from time-series approaches and explains that changes or upgrades can permit additional generation. Avoid treating a plotted value as a fixed physical ceiling for every configuration.
Check whether a value refers to generation or load, incremental or total capacity, feeder-wide or local results, and firm or managed operating conditions. Keep module kW DC, inverter kW AC and permitted export power separate. A generation result does not automatically describe battery charging or a new large load.
How to use a utility map
| Check | What to record |
|---|---|
| Network match | Utility, service location and proposed point of interconnection |
| Data identity | Map layer, methodology, timestamp and circuit/segment identifier |
| Capacity basis | Units, generation/load meaning and total versus remaining capacity |
| Constraints | Displayed limiting criteria and any exclusions or missing local equipment |
| Project basis | Inverter rating, export request, load profile and storage/control proposal |
| Next step | Current application process and questions for the utility’s engineering team |
As a current utility example, PG&E’s Grid Resource Integration Portal guidance says map information is illustrative, can change with circuit conditions and does not guarantee a connection or timeline. Its page also distinguishes government permitting from utility interconnection. That is PG&E’s published scope, not a universal map legend or queue rule.
Recheck current data at the relevant decision stage. If no public map exists, ask the utility what screening information and review route it offers. A green color or apparent spare capacity should not be presented as approval in a proposal.
Storage, inverter controls and export limits
Controls or equipment changes may alter network impacts, but their acceptance depends on the utility and applicable requirements. Storage can absorb energy only within its charging-power, energy-capacity and operating limits; a full or unavailable battery cannot indefinitely absorb surplus generation. Grid-support settings can also affect reactive power, available active power or curtailment.
Consider a hypothetical instantaneous balance: PV supplies 100 kW AC and site load is 40 kW. Without storage, unconstrained export would be 60 kW. If an accepted control scheme limits export to 30 kW, the other 30 kW must be absorbed by an available charging load or curtailed. A battery with 10 kW of available charging power could absorb only 10 kW in this simplified case, leaving 20 kW to curtail. Its kWh rating alone cannot resolve the power mismatch.
That example is a power balance, not a hosting-capacity study or proof of an approved control system. Annual curtailment and economics need time-series production, load, storage operation and applicable export conditions. See grid export limitation and curtailment modeling.
Practical handoff for solar teams
Designers should retain the map snapshot and project assumptions, then ask what evidence the utility needs for the actual connection. Develop alternatives such as a changed export request, control arrangement or upgrade only as options for review, not guaranteed workarounds.
Installers should follow accepted designs and utility-required commissioning requirements with qualified personnel. Do not access utility equipment or change inverter grid settings based solely on a screening map. Equipment labels visible from a safe location cannot establish the full network’s available capacity.
Sales and development teams should separate technical screening, formal review, cost allocation and permission to operate. Do not promise a fixed timeline, first-come entitlement or avoided upgrade cost. Document unresolved interconnection conditions alongside land-use and building approvals. Distributed generation describes the resource context; the interconnection queue concerns the applicable application process.
Frequently asked questions
Does sufficient mapped capacity guarantee approval?
No. Confirm the map’s assumptions and limitations, then follow the utility’s current project-specific interconnection process.
Can capacity change?
Yes. Network changes, new resources, loads and operating assumptions can alter study results. Use the current data and distinguish changes from reserved project rights.
Does adding a battery always avoid upgrades?
No. Charging limits, state of charge, controls and accepted operating conditions matter. Review the actual arrangement and its network impacts.
Is hosting capacity just transformer capacity minus existing solar?
No. A network study accounts for electrical and operating conditions that a simple nameplate subtraction misses.
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.
