CAISO node intelligence

WEBER

SAN JOAQUIN (CA) · PGAE · node key WEBER · CAISO run date 2026-10-12

Seven questions a developer, lender or counsel asks before filing here. Every figure is a CAISO row; Not public marks what the public files cannot answer and where to get it. Definitions: methodology.

Can you get in?

No official Cluster 16 availability statement names this POI. Absence of a statement is not availability.

Not public: per-constraint transmission headroom at this POI — CAISO's cluster study reports (RIMS login).
Not on this site yet: the zonal transmission-capability table CAISO publishes for cluster scoring — public; the join is planned.

Who is ahead of you?

260 MW (n=1)
queued ahead of a new request (legacy + C15)
260 MW (n=1)
with an executed interconnection agreement · public report; C15 has no IA yet
45 MW (n=2)
operating at this node
0 MW
Cluster 15 requests seeking full capacity
Not public: who the interconnection customers are (the queue) — CAISO's public files carry project names only; the projects table below is the full public record. EIA-860 names the owners of what already operates nearby, not of what is queued.

Do projects leave after seeing the costs?

305 MW (n=3)
received Phase II / Facilities Study results here · any sheet, public report
0 MW (n=0)
of that, withdrew with results in hand
0.00 (n=3)
Phase II attrition (MW share)
Not public: the network upgrade cost allocated to a project here — Phase I / Phase II study reports, served through RIMS. Ask the incumbent developer or request the report; nothing public reconstructs it.

Will you be deliverable?

0 MW (n=0)
2025 TPD requested at this node
0 MW
allocated
0 MW
refused at 0 % — contracted / shortlisted (groups A+B)
0 MW
refused at 0 % — no PPA (group D)
1 / 0
2024 cycle: projects given full / partial capacity

No request from this node appears in the 2025 allocation results.

A 0 % in group D is the expected result for an uncontracted project; a 0 % in group A or B is a contracted project that did not get deliverability. Rows are joined through all three sheets, so a request whose project has since withdrawn still appears. CAISO states no reason.

Will the power be worth anything here?

The Local Capacity Technical Report does not name this substation on any area boundary: not encoded, which is not the same as outside every area.

Not on this site yet: day-ahead price history at this POI — CAISO OASIS publishes it; it is shown only for a pricing node confirmed by hand in data/poi_pnodes.csv, and this one is not confirmed yet.

Will the land pass intake?

Intake scoring under the 2023 IPE rewards site control, permitting progress and system need before study begins. Parcel, zoning, Williamson Act and CEC exclusion screens run for Kings and Kern counties (caiso-siting parcels, layers screen); results are in outputs/parcels_*.md for the nodes they were run on and are not yet rendered per node here.

Not public: landowner willingness and option terms — county assessor parcels give ownership class, not intent; owner names are withheld on purpose.

How long, and who gave up?

0 MW (n=0)
withdrawn since 2022 (both reports)
0 MW
of that, storage
0.00 (n=3)
storage churn · withdrawn storage ÷ queued + operating storage
n/a (n=0)
Cluster 15 survival · active ÷ (active + withdrawn)
25 MW (n=1)
all-time withdrawn since 2006 · mostly wind/solar-era; colour, not signal
2031-06-05
current on-line dates of active projects

Cluster-level time-to-withdrawal curves are on the Survival page; they compare process regimes, not only nodes.

Projects at this node (4)

Both reports. cod = current on-line date (public report) or proposed on-line date (Cluster 15). ia_status exists only in the public report. Cluster 15 deliverability is requested, not allocated.

project_namequeue_positionsheet_statusclusternet_mwstorage_mwdeliverabilityia_statuscodwithdrawn_date
PATHFINDER STORAGE1896ACTIVEC14260260FULL CAPACITYEXECUTED2031-06-05
CASCADE ENERGY STORAGE1272COMPLETEDC092525FULL CAPACITYEXECUTED
CASCADE ENERGY STORAGE EXPANSION1835COMPLETEDISP2020FULL CAPACITY
WEBER GRID STABILIZATION PROJECT1026WITHDRAWNC072525FULL CAPACITY2016-12-312015-06-18

TPD allocation requests at this node (1)

CAISO Transmission Plan Deliverability allocation results, joined on queue position through all three sheets of the public report (a request whose project has since withdrawn still appears). 2024 rows carry no MW. Groups: A = executed power purchase agreement requiring FCDS, or an LSE serving its own load; B = shortlisted for, or actively negotiating, a power purchase agreement; C = already in commercial operation for the capacity seeking TP deliverability; D = no PPA; electing the Section 8.9.2.3 (financial-security) path.

tpd_yearqueue_idproject_nameallocation_groupmw_requestedallocation_pctmw_allocatedstatus
20241896PATHFINDER STORAGEA100%FCDSA

WDAT requests at this substation (65)

WDAT = distribution-level queue at the same substation, PG&E file today; not CAISO deliverability. WDAT requests connect below CAISO's transmission grid; they carry no CAISO deliverability unless separately studied.

showing 50 of 65

queue_positionstatus_rawprocessgen_typenet_mwrequest_receivedcurrent_codia_statusft_over_cap
3278-RDActiveDetailed StudySolar PV62023-02-07Executed
4212-RDActiveFast TrackSolar PV52025-03-21Executedheld out: >5 MW
4480-RDActiveDGSPSolar PV42025-10-02
4652-RDActiveFast TrackSolar PV32026-01-15
4306-RDActiveFast TrackSolar PV32025-06-13Executed
4307-RDActiveFast TrackSolar PV22025-06-13Executed
3449-RDActiveDGSPSolar PV12023-04-12Executed
4600-WDActiveFast TrackSolar PV12026-04-20
4130-RDActiveDGSPSolar PV12024-11-05Executed
4119-RDActiveDetailed StudySolar PV12024-11-01Executed
4120-RDActiveDGSPSolar PV12024-10-29Executed
3204-WDActiveFast TrackSolar PV12022-11-04Executed
3206-WDActiveFast TrackSolar PV12022-11-04Executed
4602-WDActiveFast TrackSolar PV12026-04-20Tendered
4598-WDActiveFast TrackSolar PV12026-04-20
3996-RDActiveFast TrackSolar PV12024-05-15Executed
2747-RDActiveDetailed StudySolar PV, Storage02021-03-032026-01-26Executed
1240-RDIn ServiceFast TrackTurbine102015-07-082017-01-26Executedheld out: >5 MW
0227-WDIn ServiceIndependent StudyEngine42010-12-302014-01-06Executed
2353-RDIn ServiceDetailed StudySolar PV32019-10-182023-01-03Executed
1790-RDIn ServiceFast TrackSolar PV12018-01-022021-08-17Executed
2633-RDIn ServiceFast TrackSolar PV12020-10-192021-10-19Executed
1791-RDIn ServiceDetailed StudySolar PV12018-01-022021-08-17Executed
1749-RDIn ServiceFast TrackSolar PV12017-11-062020-07-03Executed
2016-RDIn ServiceFast TrackSolar PV12018-07-022019-02-01Executed
4450-WDWithdrawnDGSPSolar PV52025-09-26Withdrawn
4451-WDWithdrawnDGSPSolar PV52025-09-26Withdrawn
4452-WDWithdrawnDGSPSolar PV52025-09-26Withdrawn
4453-WDWithdrawnDGSPSolar PV52025-09-26Withdrawn
4454-WDWithdrawnDGSPSolar PV52025-09-26Withdrawn
4455-WDWithdrawnDGSPSolar PV52025-09-26Withdrawn
4458-WDWithdrawnDGSPSolar PV52025-09-26Withdrawn
4461-WDWithdrawnDGSPSolar PV52025-09-26Withdrawn
3383-RDWithdrawnDetailed StudySolar PV42023-04-04Withdrawn
0207-WDWithdrawnIndependent StudySolar PV42010-11-23Withdrawn
0210-WDWithdrawnIndependent StudySolar PV42010-11-23Withdrawn
0216-WDWithdrawnIndependent StudySolar PV42010-11-29Withdrawn
4235-WDWithdrawnFast TrackSolar PV32025-04-06Withdrawn
4236-WDWithdrawnFast TrackSolar PV32025-04-06Withdrawn
4237-WDWithdrawnFast TrackSolar PV32025-04-06Withdrawn
4238-WDWithdrawnFast TrackSolar PV32025-04-06Withdrawn
4239-WDWithdrawnFast TrackSolar PV32025-04-06Withdrawn
4240-WDWithdrawnFast TrackSolar PV32025-04-06Withdrawn
4241-WDWithdrawnFast TrackSolar PV32025-04-06Withdrawn
4242-WDWithdrawnFast TrackSolar PV32025-04-06Withdrawn
4243-WDWithdrawnFast TrackSolar PV32025-04-06Withdrawn
4244-WDWithdrawnFast TrackSolar PV32025-04-06Withdrawn
4245-WDWithdrawnFast TrackSolar PV32025-04-06Withdrawn
4246-WDWithdrawnFast TrackSolar PV32025-04-06Withdrawn
4456-WDWithdrawnDGSPSolar PV32025-09-26Withdrawn

Geocode provenance

Position is approximate or unknown (county-centroid): position unknown; placed at the median of located nodes in the county.

geo_method
county-centroid
geo_score
0.30
osm_name
median of located nodes in CA SAN JOAQUIN
lat, lon
37.77704, -121.31473

All metrics

metricvaluedefinition
legacy_active_mw260active MW in the public report (C14 and earlier)
c15_active_mw0active MW in the Cluster 15 report
operating_mw45completed MW in the public report
pipeline_storage_mw260storage MW inside legacy_active_mw + c15_active_mw
operating_storage_mw45storage MW inside operating_mw (completed, public report)
wd_recent_mw0withdrawn in the last 5 years (both reports)
wd_recent_storage_mw0storage MW of those rows — each project's storage components capped at its net-to-grid figure; a handful of filings report net-to-grid as 0 and keep the component MW, so this can exceed the row above at 3 nodes.
wd_post_phase2_mw0withdrew AFTER Phase II / Facilities Study results (public report only)
p2_reached_mw305MW of projects that received Phase II / Facilities Study results here (public report, any sheet)
p2_withdrawn_mw0of those, MW that then withdrew (== wd_post_phase2_mw)
p2_attrition0.00p2_withdrawn_mw / p2_reached_mw — share of studied MW that left with results in hand
committed_mw260ACTIVE MW holding an executed interconnection agreement (public report)
churn_n3projects behind storage_churn (withdrawn recent + queued + operating)
c15_n0projects behind c15_survival
p2_n3projects behind p2_attrition
eia_plants0operable EIA-860 plants within 5 km of the node's mapped position (positioned nodes only)
eia_nameplate_mw0their nameplate MW, all technologies (EIA-860 Generator file, Operable sheet)
eia_storage_mwh0battery energy capacity among them (EIA-860 Energy Storage file), as reported
eia_storage_1h_mwstorage MW at units whose reported MWh is no more than their MW (one hour or less); shown with 'duration not established' because the value may reflect how the form was filled
eia_proposed_mw0nameplate MW in EIA-860's Proposed sheet within the same radius (planned / under construction)
wd_alltime_mw25every withdrawn MW since 2006 (includes dead wind/solar-era projects)
storage_churn0.00wd_recent_storage_mw / (active + operating storage MW) — the one to quote
churn_alltime0.08wd_alltime_mw / (pipeline + operating MW) — historical color only
c15_survivaln/ac15_active / (c15_active + c15_withdrawn)
c15_fcds_req_mw0C15 active MW that requested Full Capacity Deliverability Status (requested, not allocated)
tpd25_projects0projects at the node that sought TPD in CAISO's 2025 allocation cycle
tpd25_req_mw0MW at the node that sought TPD in CAISO's 2025 allocation cycle
tpd25_alloc_mw0MW allocated in that cycle (requested × allocation %)
tpd25_denied_mw0MW requested by rows that received 0 %
tpd25_unalloc_mw0requested minus allocated: MW refused outright PLUS the remainder left by partial allocations — quote this for 'what the developer did not get'
tpd25_unknown_mw0MW requested by rows with no allocation percentage in the file; 0 today
tpd25_req_A_mw0of tpd25_req_mw, requested in allocation group A: executed PPA (or LSE own load)
tpd25_req_B_mw0of tpd25_req_mw, requested in allocation group B: shortlisted / negotiating a PPA
tpd25_req_C_mw0of tpd25_req_mw, requested in allocation group C: already in commercial operation
tpd25_req_D_mw0of tpd25_req_mw, requested in allocation group D: no PPA, Section 8.9.2.3 path
tpd25_denied_A_mw0of tpd25_denied_mw, refused at 0 % in group A
tpd25_denied_B_mw0of tpd25_denied_mw, refused at 0 % in group B
tpd25_denied_C_mw0of tpd25_denied_mw, refused at 0 % in group C
tpd25_denied_D_mw0of tpd25_denied_mw, refused at 0 % in group D
tpd25_denied_ppa_mw0refused MW in groups A + B: contracted or shortlisted projects that did not get deliverability; the refusal that matters
tpd24_fcdsa_projects1projects at the node allocated Full Capacity in the 2024 cycle
lcr_statusCAISO Local Capacity Area (Resource Adequacy geography): 'in <area>' or 'outside <area>' as the LCT report's boundary lists state it; blank = not encoded, never 'outside every area'
lcr_sub_areasub-area / load pocket within that area, when the LCT report delineates it
wdat_active_projects16active WDAT requests at the same substation (WDAT = distribution-level queue at the same substation, PG&E file today; not CAISO deliverability)
wdat_active_mw29MW of active WDAT (distribution-level) requests at the same substation (PG&E file today)
wdat_active_storage_mw0storage MW attributed from wdat_active_mw — an assumption: the PG&E file publishes one MW figure per request, so storage-only requests count in full and solar+storage requests count at half (160 of 1,011 active requests carry storage; 362 of their 479 MW is attributed as storage).
wdat_inservice_mw22WDAT MW already in service at that substation
wdat_withdrawn_mw120WDAT MW withdrawn at that substation (all-time in the file)
wdat_ft_over_cap_n1active Fast Track requests above the 5 MW Fast Track ceiling — held out of wdat_active_*
wdat_ft_over_cap_mw5MW of those held-out rows, as posted; cause not established

No figure on this site states a cause. CAISO files carry no withdrawal reason beyond "IC Request".

Screening tool, not engineering advice. Built from public filings by an engineer who is not a licensed PE. Verify every figure against the source filing named in its row before you rely on it for any decision. No warranty of any kind. Not affiliated with CAISO, EIA, or any utility. No engineering services are offered.