Queue projects

Every active interconnection queue project in the seven U.S. ISO/RTO markets, surfaced as its own detail page. Queue projects sit alongside operating plants in InfraSure's open data foundation — same asset spine, same cross-referencing discipline, and the same forward-looking analytical-layer teasers from the InfraSure platform.

Queue projects are intrinsically forward-looking: they don't exist yet, so every question about them is forward. That makes them the natural fit for the analytical-layer teasers — risk analytics, generation forecast, financial forecast — even before the InfraSure platform ships their full depth.

What's on a queue project page

The page mirrors the plant detail layout: a sticky left rail with 13 sections, a hero with grid-region attribution, and section content organized by diligence flow.

• Hero + KPI cards. Project name, queue ID, capacity, technology, status, queue date, proposed COD, state + county, ISO/RTO. Grid-region card on the right (BA, ISO/RTO, NERC, RC).
• Status + interconnection. IA status, study phase, service type, point of interconnection, queue date timeline. Where the queue project actually stands.
• Risk Analytics teaser. Mock composite score (deterministic from queue_id) — the InfraSure platform produces the real risk decomposition for the project under actual hazard, generation, and counterparty assumptions.
• Technology + about + details. Component breakdown (e.g., Solar 200 MW + Battery 100 MW hybrid). Developer, utility, project type. Identifiers and metadata.
• Forward outlook teasers. Generation Forecast and Financial Forecast — what the asset will produce, what it will earn, under probabilistic scenarios. Available in the InfraSure platform.
• Pricing. Nodal LMP context where available — POI-geocoded.
• EIA Match. When a queue project has been matched to an existing EIA plant (commissioned or under-construction), the page surfaces the link.
• News + Ask Pi reports. Classified news linked to the queue project, plus any persisted Ask Pi report results.

Coverage

9,783 active queue projects across CAISO, ERCOT, MISO, PJM, SPP, NYISO, ISO-NE. Sourced from LBNL Interconnection Queues + direct ISO/RTO queue exports. Each project is cross-referenced; the InfraSure team has resolved developer and utility entity names across upstream sources where the source data varies.

URL patterns

Queue project pages use slug URLs:

/project/{slug}
  → e.g. /project/ercot-29inr0271-los-toros-energy-center-storage-slf

/api/project/{slug}                 JSON (full record)
/api/project/{slug}/text            Markdown summary
/api/projects                       Index of all 9,783 projects
/api/projects/search                Slim search index

See also

• Plant detail pages — same layout, applied to operating assets.
• APIs — programmatic access to project data.
• InfraSure platform: Evaluate — forward-looking analytics for queue projects on the platform.