Interconnection Queue Monitor avatar

Interconnection Queue Monitor

Pricing

from $5.00 / 1,000 results

Go to Apify Store
Interconnection Queue Monitor

Interconnection Queue Monitor

Monitors US grid interconnection queues (CAISO, PJM, MISO) and reports every project change as structured data: new applications, withdrawals, capacity and COD changes, study-phase progress. Filter by fuel, state and size.

Pricing

from $5.00 / 1,000 results

Rating

0.0

(0)

Developer

Kasım Genç

Kasım Genç

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

12 days ago

Last modified

Share

Monitors US grid interconnection queues — the official waiting lists of every power plant and battery project seeking to connect to the grid — and reports each change as structured data:

  • "A new 200 MW battery project entered the PJM queue in Ohio."
  • "This solar project moved from Phase 1 to GIA — it's getting real."
  • "Competitor X's project was withdrawn." / "Project Y just reached commercial operation."
  • "The proposed COD slipped two years."

Coverage: CAISO (California), PJM (13 Mid-Atlantic/Midwest states), MISO (15 Central US states) — together roughly 15,000 tracked queue positions. Sources are the ISOs' official public queue reports. (ERCOT, NYISO, ISO-NE are on the roadmap; their downloads sit behind aggressive bot protection.)

Who uses this

  • Project developers — track competing projects near your POI, spot withdrawals that free up headroom.
  • Land agents & site originators — new queue entries reveal who is developing where, months before permits.
  • Equipment vendors & EPCs — projects advancing to later study phases are buying signals.
  • Investors & analysts — queue trends by fuel/region without manually diffing spreadsheets.

How it works

Each run downloads the current queue from every selected ISO, normalizes projects into a common shape, and diffs them against the snapshot from the previous run (kept in a named key-value store). Only changes matching your filters are output. Schedule it daily or weekly for a continuous feed.

  • The first run per ISO establishes the baseline (silent by default — see emitBaselineRecords).
  • If an ISO's download fails, its snapshot stays untouched and the other ISOs still process — a flaky source can't produce phantom changes.
  • Withdrawn-to-withdrawn noise is suppressed unless you opt in (includeWithdrawn).

Input

{
"isos": ["CAISO", "PJM", "MISO"],
"fuels": ["solar", "battery", "hybrid"],
"states": ["CA", "OH", "IL"],
"minCapacityMW": 50,
"emitBaselineRecords": false
}
FieldTypeDescription
isos *string[]CAISO, PJM, MISO (any subset).
fuelsstring[]solar, wind, battery, hybrid (co-located, e.g. solar+storage), gas, nuclear, hydro, geothermal, biomass, coal, oil, other. Empty = all.
statesstring[]2-letter codes. Empty = all.
minCapacityMWintegerMinimum project size. Default 0.
includeWithdrawnbooleanAlso track projects that are already withdrawn. Transitions into withdrawn are always reported. Default false.
emitBaselineRecordsbooleanPush all matching projects as baseline on the first run. Queues are large (PJM ~9,000 rows) — leave off unless you want the full current picture. Default false.
snapshotStoreNamestringNamed KV store for snapshots between runs.

Output

One dataset record per changed project, largest capacity first:

{
"iso": "CAISO",
"queueId": "CAISO-17",
"projectName": "SONORAN 2",
"state": "CA",
"county": "RIVERSIDE",
"utility": "SCE",
"poi": "Colorado River Substation 230 kV",
"fuel": "hybrid",
"fuelRaw": "Photovoltaic + Battery",
"capacityMW": 400,
"status": "withdrawn",
"previousStatus": "active",
"statusRaw": "WITHDRAWN",
"studyPhase": "IA: Executed",
"queueDate": "2019-04-10",
"proposedCOD": "2027-06-01",
"changeType": "project_withdrawn",
"changes": [
{ "field": "status", "kind": "status_changed", "old": "active", "new": "withdrawn" }
],
"queueUrl": "https://www.caiso.com/library/public-queue-report",
"detectedAt": "2026-07-10T15:41:05.892Z",
"source": "CAISO public interconnection queue"
}

changeType values

ValueMeaning
baselineFirst run for an ISO — current state of a project (opt-in).
new_projectNew queue entry appeared.
project_withdrawnProject left the queue (withdrawn/retracted/canceled).
project_in_serviceProject reached commercial operation.
project_suspendedProject suspended.
status_changedOther status transition.
capacity_changedMW figure changed (see oldCapacityMW).
cod_changedProposed/actual commercial operation date changed (see previousCOD).
phase_changedStudy phase / interconnection agreement status advanced.
project_updatedOther material change (POI, name, transmission owner).
removed_from_queueRow disappeared from the source report entirely.

The run summary (per-ISO counts, failures) is stored under the OUTPUT key of the default key-value store.

Data sources & update cadence

ISOSourceTypical update
CAISOPublic Queue Report (XLSX)~monthly
PJMPlanning API queue export (XLSX)~daily
MISOGI Queue API (JSON)~weekly

Daily scheduling is safe — unchanged sources simply produce zero records.