Public evidence index / CAISO queue-history bundle
See how CAISO interconnection projects moved across published queue reports
A one-time dataset of the California ISO generator interconnection queue, rebuilt from 25,058 project-date observations covering 2,278 distinct project IDs across 11 captured dates. The $249 direct-file bundle shows what each published report said on each date instead of presenting only the latest workbook.
This is an observation record, not an assessment. It reports what the published queue said on the dates captured. It does not predict approval, forecast dates, interpret CAISO policy, or turn a missing source capture into a project event.
Scope boundary: Only California ISO (CAISO) is included in the paid bundle described here. SPP, ISO New England, NYISO, MISO, and ERCOT are not sold in this bundle. AWS Data Exchange procurement and AWS-native delivery are also not offered on this page.
Request the CAISO bundle scope →
The request takes no payment and creates no order. We confirm the observation window, file contract, intended use, and delivery address in writing before offering a one-time payment path.
The fixed deliverable
$249 one time
After written scope acceptance and payment, receive five files within 3 business days. There is no subscription to cancel, no recurring collector access, and no claim that the archive contains every date on which CAISO changed its workbook.
- Project-date CSV. One normalized row per project and captured report date, with the source values retained as published.
- Project-date JSONL. The same observation rows in pipeline-friendly records.
- Dataset card. Field definitions, the 11-date coverage window, known gaps, attribution, and interpretation limits.
- Source-rights receipt. The reviewed CAISO source and terms URLs, retrieval status, file digest, and the inclusion decision.
- SHA-256 manifest. A digest for each delivered file so the buyer can identify the exact bytes received.
Ask whether this window fits your workflow →
A request is accepted or declined before payment. Custom ISO additions, forecasts, policy opinions, interconnection advice, and continuous monitoring are outside this fixed scope.
Useful buyers include transmission developers, infrastructure diligence teams, energy-data product managers, and researchers who need reproducible project-date rows rather than an unlabeled “current versus old” spreadsheet comparison. The bundle is intended for a buyer who can work with CSV or JSONL and wants source identity to travel with each delivery.
What the archive actually observed
The counts below were recomputed on 2026-08-09 from the owned SQLite archive opened in read-only mode. They describe only the CAISO observation window from 2026-06-11 through 2026-08-09; they are not counts for the full history of the interconnection market.
- 25,058 project snapshots across 2,278 distinct project IDs.
- 11 observation dates, from 2026-06-11 through 2026-08-09.
- 15 projects had a compared field differ across consecutive captured reports.
- The observed differences were 14 status-field differences and 1 project-name difference.
A difference is just a source-field difference between files. It is not evidence of why a field changed, whether a development milestone occurred, or whether a later value is more authoritative. The initial observation is never labeled a change. A project absent from an uncaptured or unreachable report is never labeled withdrawn. Those distinctions are carried into the dataset card so a coverage gap cannot masquerade as a market event.
Source and attribution
Source: California Independent System Operator (California ISO or CAISO), Public Queue Report workbook. The latest source file fetched for this review returned HTTP 200 on 2026-08-09; its retained receipt records 385,087 bytes and SHA-256 894b12c83c4574a165b17ba16881608a869a98854064d6d7691d95d59c2fd52e.
The inclusion review also fetched the CAISO privacy and terms page and the CAISO robots file. The terms permit use of most site materials when applicable notices remain intact and California ISO receives credit. Every derived artifact therefore identifies and credits California ISO, links the report source, carries the retrieval date, and preserves applicable source notices. The bundle is an independent US Tech Automations product; California ISO does not sponsor or endorse it.
The SHA-256 identifies retrieved bytes. It does not prove that the source is current today, establish an ISO filing, or confer rights beyond the reviewed source conditions. Buyers should refetch the official report before making a filing, investment, construction, or operational decision.
Why the other five regions are not included
A source being publicly reachable does not by itself grant commercial redistribution rights. The 2026-08-09 review used each operator's official terms, legal notice, or robots policy and kept every unresolved source outside the paid file set.
| Region | Bundle outcome | Observed boundary |
|---|---|---|
| California ISO | INCLUDED WITH ATTRIBUTION | The official report and terms were fetched; attribution and notice conditions travel with the files. |
| Southwest Power Pool | EXCLUDED | Official portal terms require express written authorization for commercial use; no authorization is recorded. |
| ISO New England | EXCLUDED | The official legal page warns about duplication and non-personal use; no commercial redistribution grant was found. |
| New York ISO | EXCLUDED | The workbook path was not barred by robots, but the official legal notice provides no content license. Robots allowance is not a license. |
| Midcontinent ISO | WITHHELD | The established identifying collector received HTTP 403. The current robots policy was recorded; the collector was not disguised as a browser. |
| ERCOT | WITHHELD | The current robots file disallows the exact report-listing and download path prefixes. Neither target was fetched for this review. |
These are product inclusion decisions, not legal opinions about every possible use. A later source-policy change, direct operator license, or documented authorization would require a new review and a separately versioned scope. Until then, the direct bundle stays CAISO-only.
AWS Data Exchange boundary
A machine check on 2026-08-09 could not establish provider qualification for this product and found no buyer-facing AWS Data Exchange listing URL. The machine verdict is therefore UNKNOWN, never approved or denied. The offer on this page is direct file delivery only.
AWS documents a separate provider registration and qualification process and publishing guidelines. Creating source files does not establish that a buyer can procure them through AWS. No AWS subscription, listing availability, approval, partnership, or endorsement is represented here.
If AWS Data Exchange is a mandatory procurement channel, do not request this direct-file pilot. The relevant future evidence would be a fetched buyer-facing product URL and a machine-confirmed provider state; neither is present in this offer.
Request and fit check
Use the partner form to name your workflow, whether CSV or JSONL is primary, and whether the stated 11-date window is useful. Do not send credentials, restricted files, project secrets, or personal information. The fit check asks only for coarse business requirements.
A suitable request needs the existing CAISO window, accepts direct file delivery, and treats observed source differences as observations. A request that requires a different ISO, a causal event feed, financial or legal conclusions, investment advice, AWS procurement today, guaranteed future collection, or private third-party data is declined before payment.
Request a no-payment scope check →
Browse other data services · Browse public evidence · Explore the free grid queue pages