Use a utility Integration Capacity Analysis (ICA) / hosting capacity map to pre-screen a project site before submitting an interconnection application
domain: solar.interconnection · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify whether the project's utility publishes a public ICA/hosting-capacity map — California's three major IOUs (PG&E, SCE, SDG&E) each provide one as part of CPUC's Data Portals requirement (e.g., SDG&E's Interactive Map and ICA tool)
Look up the specific circuit/feeder serving the project address and check available hosting capacity for new generation at that location before finalizing system size
Review the interconnection queue information shown on the map to understand how much capacity from other pending projects is already claimed ahead of a new application on that circuit
For larger commercial projects near a capacity-constrained circuit, factor potential upgrade costs or queue delays into the proposal timeline rather than assuming standard turnaround
Use the ICA data as a planning input only — final interconnection feasibility is still determined by the utility's formal application review, not by the public map alone
Known gotchas
ICA/hosting-capacity data is a planning screen, not a guarantee — actual interconnection approval still depends on the utility's formal engineering review at application time, which can find constraints the public map didn't show
Map data can lag real-time queue changes — a circuit shown as having capacity can fill from other applications between when the map is checked and when a new application is submitted
Each utility publishes its own ICA tool with different interfaces and update cadences — don't assume the same navigation or data freshness across different utility territories
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?