{ "agent_answer": { "answer": "SPP's GI queue lists project GI-SISS-2026-04 (Battery/Storage/\u2014) requesting 150.0 MW near Kit Carson County,, CO \u2014 status DISIS STAGE \u2014 as of 2026-06-22 (requested, not built).", "citation": { "as_of": "2026-06-22", "raw_file_sha256": "b7ee16555e89c6eee5ce7393e3129c74e5148ca72d0f85366ee80b53aed123f7", "sheet": "GI_Summary", "source_file": "spp-gi_2026-06-22_sample.csv", "source_id": "energy.spp.queue", "source_row": 37, "source_url": "https://opsportal.spp.org/Studies/GISummary" }, "question": "Which SPP queue project can be verified from the raw GI Summary CSV row?", "verification": { "hash_verified": true, "raw_file_sha256": "b7ee16555e89c6eee5ce7393e3129c74e5148ca72d0f85366ee80b53aed123f7", "sheet": "GI_Summary", "source_file": "spp-gi_2026-06-22_sample.csv", "source_row": 37 } }, "goal": "Use the agent-facing tool contract to discover, query, and verify power.interconnection_queue_spp.", "steps": [ { "params": {}, "result": { "combinable_on": { "balancing_authority_code": [ "power.asset_ownership", "power.capacity", "power.demand", "power.fuel_cost", "power.generation" ], "county_fips": [ "ai_infrastructure.employment", "power.capacity", "power.interconnection_queue", "power.interconnection_queue_caiso", "power.interconnection_queue_ercot", "power.interconnection_queue_isone", "power.interconnection_queue_nyiso", "power.interconnection_queue_pjm", "power.interconnection_queue_pjm_cycle", "power.interconnection_queue_spp" ], "eia_plant_id": [ "power.asset_ownership", "power.capacity", "power.fuel_cost", "power.generation" ], "generator_id": [ "power.asset_ownership", "power.capacity", "power.generation" ], "state": [ "ai_infrastructure.employment", "natural_gas.prices", "power.asset_ownership", "power.capacity", "power.fuel_cost", "power.generation", "power.interconnection_queue", "power.interconnection_queue_caiso", "power.interconnection_queue_ercot", "power.interconnection_queue_isone", "power.interconnection_queue_nyiso", "power.interconnection_queue_pjm", "power.interconnection_queue_pjm_cycle", "power.interconnection_queue_spp", "power.price_ercot", "power.retail_sales", "robotics.adoption", "space.satellite_filings" ] }, "compounds": [ { "definition": "capacity_factor = sum(net_generation_mwh) / (sum(operating nameplate_mw) \u00d7 hours_in_month), over plant\u00d7fuel present in BOTH EIA-923 (generation) and EIA-860M operating capacity (snapshot matched to the month). Storage excluded; basis = nameplate.", "id": "power.capacity_factor", "kind": "compound", "metric": "capacity_factor", "primitive": "query_capacity_factor_v1", "sources": [ "energy.eia.eia860m", "energy.eia.eia923" ], "title": "Power Capacity Factor" } ], "domains": [ { "capabilities": [ { "anchors": [ "county_fips", "state", "lat", "lon", "eia_plant_id", "generator_id", "balancing_authority_code" ], "answers": [ "operating generator capacity by location, fuel, technology, and source-reported balancing authority code", "planned generator capacity by location, fuel, technology, source-reported balancing authority code, and planned online year", "retired generator capacity by location, fuel, technology, source-reported balancing authority code, and retirement year" ], "current_sources": [ "energy.eia.eia860m" ], "id": "power.capacity", "primitive": "query_power_capacity_v1", "product_spec": "blocks/power_capacity/card.md", "represented_facts": [ "EIA-860M reports operating generator capacity by location, fuel, technology, status, and source-reported balancing authority code", "EIA-860M reports planned generator capacity by location, fuel, technology, status, source-reported balancing authority code, and planned online year", "EIA-860M reports retired generator capacity by location, fuel, technology, status, source-reported balancing authority code, and retirement year" ], "status": "available", "title": "Power Capacity" }, { "anchors": [ "eia_plant_id", "state", "balancing_authority_code", "generator_id" ], "answers": [ "monthly net generation (MWh) by plant, prime mover, and fuel", "monthly net generation (MWh) by individual generator, joinable to EIA-860M", "generation mix by state, balancing-authority code, and fuel over time", "total and electric-only fuel consumption (MMBtu), aligned to Page 1 net generation across the served 2014-to-present history" ], "current_sources": [ "energy.eia.eia923" ], "id": "power.generation", "primitive": "query_power_generation_v1", "product_spec": "blocks/power_generation/card.md", "represented_facts": [ "EIA-923 reports monthly net electricity generation (MWh) by plant, prime mover, and fuel (Page 1)", "The same Page 1 source row reports total fuel consumed and fuel consumed for electricity separately in MMBtu", "EIA-923 reports monthly net electricity generation (MWh) by individual generator (Page 4), joinable to EIA-860M" ], "status": "available", "title": "Power Generation" }, { "anchors": [ "state", "eia_plant_id", "generator_id", "balancing_authority_code" ], "answers": [ "raw annual EIA-860 owner names and fractional ownership shares by plant and generator", "ownership rows for a raw owner-name string, with no name normalization or entity matching", "same-vintage state and source-reported balancing-authority slices, including ERCO", "the explicit EIA default that absence from the Owner schedule means wholly owned by the operator" ], "current_sources": [ "energy.eia.eia860_owner" ], "id": "power.asset_ownership", "primitive": "query_power_asset_ownership_v1", "product_spec": "blocks/power_asset_ownership/card.md", "represented_facts": [ "Annual EIA-860 reports the raw ownership shares and owner identities for generators that are jointly owned or wholly owned by an entity other than the operator. A generator absent from the Owner schedule is wholly owned by its operator, as EIA explicitly documents; the block carries same-vintage generator/operator context so consumers can apply that default without treating absence as unknown ownership.", "Owner-schedule absence means wholly owned by the same-vintage generator operator." ], "status": "available", "title": "Power Asset Ownership" }, { "anchors": [ "state", "eia_plant_id", "balancing_authority_code" ], "answers": [ "raw receipt-level delivered fuel costs in cents per MMBtu and physical quantities", "receipt rows by plant, month, fuel, state, supplier, purchase type, or source-reported balancing authority", "explicit counts and records for reported versus withheld fuel costs" ], "current_sources": [ "energy.eia.eia923_receipts_cost" ], "id": "power.fuel_cost", "primitive": "query_power_fuel_cost_v1", "product_spec": "blocks/power_fuel_cost/card.md", "represented_facts": [ "EIA-923 Page 5 reports individual fossil-fuel receipts by plant and month, including raw physical quantity and delivered fuel cost in cents per MMBtu. Confidential or otherwise unpublished costs remain explicit missing values; they are never zero-filled, imputed, or converted into heat rates or $/MWh.", "Withheld EIA fuel-cost cells are explicit nulls with the raw marker preserved." ], "status": "available", "title": "Power Fuel Receipts and Costs" }, { "anchors": [], "answers": [ "as-filed large-steam plant capacity, net generation, plant balances, fuel expense, and separate O&M line items", "raw respondent and plant-name searches without normalization or EIA matching", "which Form 1 respondents and raw plant names have served data for a report year", "a one-call ERCOT-relevance slice based only on the respondent's raw states-served disclosure" ], "current_sources": [ "energy.ferc.form1_plant_costs" ], "id": "power.plant_costs", "primitive": "query_power_plant_costs_v1", "product_spec": "blocks/power_plant_costs/card.md", "represented_facts": [ "Accepted native-XBRL FERC Form 1 filings report as-filed large steam-electric plant statistics by respondent, year, and raw plant name: installed capacity, net generation, plant-cost balance facts, and separate production-expense line items. Dollar values are nominal and are never inflation-adjusted, allocated, or summed into a derived O&M total." ], "status": "available", "title": "FERC Form 1 Plant Costs" }, { "anchors": [ "state" ], "answers": [ "daily Henry Hub spot prices in EIA's published dollars-per-MMBtu unit", "monthly state-average prices paid by electric-power consumers in EIA's published dollars-per-Mcf unit", "exact source-null state-month records, never zero-filled", "Texas monthly electric-power prices in one state-filtered call", "per-series coverage windows and separately queryable revision vintages" ], "current_sources": [ "energy.eia.natural_gas_prices" ], "id": "natural_gas.prices", "primitive": "query_natural_gas_prices_v1", "product_spec": "blocks/natural_gas_prices/card.md", "represented_facts": [ "EIA publishes the daily Henry Hub natural-gas spot price in dollars per MMBtu and monthly state-average natural-gas prices paid by electric-power consumers in dollars per Mcf. The state series is an aggregate of what the state's power sector paid in that month, not a plant-level price. Source-null state-month values remain explicit nulls and revisions remain separate capture vintages.", "Source-null state-month prices remain explicit nulls, and mixed source units are never blended." ], "status": "available", "title": "Natural Gas Prices" }, { "anchors": [ "balancing_authority_code" ], "answers": [ "hourly observed electricity demand (MW) for a balancing authority (Adjusted series, cited to the source row)", "the day-ahead demand forecast for the same BA-hours \u2014 forecast-vs-actual misses", "which hours EIA imputed rather than metered (is_imputed)", "BA-level demand shape over time (daily/seasonal profiles, growth at BA grain)" ], "current_sources": [ "energy.eia.eia930" ], "id": "power.demand", "primitive": "query_power_demand_v1", "product_spec": "blocks/power_demand/card.md", "represented_facts": [ "EIA-930 reports hourly observed electricity demand (MW) by balancing authority \u2014 EIA's Adjusted series, with the raw value and imputation flag preserved", "EIA-930 reports the day-ahead demand forecast (MW) on the same balancing-authority-hour rows" ], "status": "available", "title": "Power Demand" }, { "anchors": [], "answers": [ "hourly observed electricity demand (MW) for the US48 national total (cited to the source record)", "hourly observed demand for any of the 13 EIA regions (CAL, CAR, CENT, FLA, MIDA, MIDW, NE, NW, NY, SE, SW, TEN, TEX)", "the day-ahead demand forecast for the same respondent-hours \u2014 forecast-vs-actual misses", "national / regional demand shape over time (daily/seasonal profiles, growth) from EIA's own published totals" ], "current_sources": [ "energy.eia.eia930_rollup" ], "id": "power.demand_rollup", "primitive": "query_power_demand_rollup_v1", "product_spec": "blocks/power_demand_rollup/card.md", "represented_facts": [ "EIA-930 reports hourly observed electricity demand (MW) as EIA's own published rollup totals \u2014 US48 (the Lower-48 national total) and the 13 EIA regions (the Adjusted series, served verbatim, not a sum)", "EIA-930 reports the day-ahead demand forecast (MW) on the same respondent-hour rows" ], "status": "available", "title": "Power Demand (national / region rollup)" }, { "anchors": [ "state", "eia_utility_id" ], "answers": [ "annual retail electricity sales (billed MWh) by utility, state, and customer sector", "annual retail revenue (thousand dollars) and customer counts at the same grain", "industrial / commercial demand-growth signals by state and utility (year over year, as vintages accumulate)", "service-type structure (bundled vs energy-only vs delivery-only) per utility and state" ], "current_sources": [ "energy.eia.eia861" ], "id": "power.retail_sales", "primitive": "query_power_retail_sales_v1", "product_spec": "blocks/power_retail_sales/card.md", "represented_facts": [ "EIA-861 reports annual retail electricity sold to ultimate customers \u2014 billed sales (MWh), revenue, and customer counts \u2014 by utility, state, and customer sector", "EIA-861 reports the filing part and service type (bundled / energy-only / delivery-only) behind each utility\u00d7state row" ], "status": "available", "title": "Power Retail Sales" }, { "anchors": [ "state", "county_fips" ], "answers": [ "which generation projects have requested to connect to the MISO grid, by state/county, fuel, technology, and status", "the requested (net summer / net winter) megawatts of each queued project, cited to its source row", "the as-reported application status, study phase, and post-GIA status of each project (kept separate, never collapsed)", "the count of queued projects in a scope (active vs withdrawn vs done \u2014 by filtering application_status)" ], "current_sources": [ "energy.miso.giqueue" ], "id": "power.interconnection_queue", "primitive": "query_power_interconnection_queue_v1", "product_spec": "blocks/power_interconnection_queue/card.md", "represented_facts": [ "MISO's generator interconnection queue reports each project's REQUESTED interconnection capacity (net summer / net winter MW) \u2014 a request, not built capacity", "MISO's queue reports each project's location (state, county), fuel and technology, three as-reported status dimensions (application status, study phase, post-GIA status), and lifecycle dates (queue, withdrawn, in-service, done)", "MISO also reports two sparse lifecycle dates served under MISO's own field labels \u2014 gia_to_exec_date and neg_in_service_date; MISO publishes no data dictionary, so these are served as-reported and not reinterpreted (present where MISO reports them, null otherwise)" ], "status": "available", "title": "Power Interconnection Queue (MISO)" }, { "anchors": [ "state", "county_fips" ], "answers": [ "which projects have requested to connect to the PJM grid, by state/county, fuel, project type, and status", "the requested (max-facility-output / net summer / net winter) megawatts of each queued project, cited to its source row", "the as-reported status of each PJM project (Active / Withdrawn / In Service / Under Construction / \u2026), kept verbatim", "the realized in-service (built) megawatts of completed PJM projects (in_service_mw), separate from requested MW", "the count of queued projects in a scope (active vs withdrawn vs in service \u2014 by filtering status)" ], "current_sources": [ "energy.pjm.queue" ], "id": "power.interconnection_queue_pjm", "primitive": "query_power_interconnection_queue_pjm_v1", "product_spec": "blocks/power_interconnection_queue_pjm/card.md", "represented_facts": [ "PJM's New Services (interconnection) queue reports each project's REQUESTED interconnection capacity (MFO / net summer / net winter MW) \u2014 a request, not built capacity", "PJM's queue reports each project's location (state, POI county), fuel and project type, the single as-reported status, the study-document URLs and per-stage statuses, and lifecycle dates", "PJM also reports in_service_mw \u2014 the realized BUILT MW for in-service projects \u2014 carried under its own name, never as a requested figure" ], "status": "available", "title": "Power Interconnection Queue (PJM)" }, { "anchors": [ "state", "county_fips" ], "answers": [ "which projects are in PJM's cluster cycles (TC1/TC2 transition, C01+ reopened), by cycle, stage, state, fuel, and status", "the requested (MFO / net summer / net winter) megawatts of each cluster-cycle project, cited to its source row", "the cluster stage / decision point and developer of each project, as PJM reports them", "the realized in-service (built) megawatts and long-term-firm transmission MW, separate from requested MW", "the count of cluster-cycle projects in a scope (e.g. cycle=C01, status=Active)" ], "current_sources": [ "energy.pjm.cycle" ], "id": "power.interconnection_queue_pjm_cycle", "primitive": "query_power_interconnection_queue_pjm_cycle_v1", "product_spec": "blocks/power_interconnection_queue_pjm_cycle/card.md", "represented_facts": [ "PJM's cluster/cycle grid reports each project's cluster cycle (TC1/TC2 transition, C01+ reopened steady-state) and stage, with its REQUESTED interconnection capacity (MFO / net summer / net winter MW) \u2014 a request, not built capacity", "PJM's cycle grid reports each project's developer, location (state, county), fuel, phased System-Impact-Study report URLs + statuses, and lifecycle dates", "PJM also reports in_service_mw (realized built MW) and ltf_mw (long-term firm transmission MW), carried under their own names; this is a separate publication from PJM's New Services queue and is never merged with it" ], "status": "available", "title": "Power Interconnection Queue (PJM cluster/cycle)" }, { "anchors": [ "state", "county_fips" ], "answers": [ "which projects have requested to connect to the CAISO grid, by state/county, fuel/technology, cluster, deliverability, and status", "the net megawatts to grid of each queued CAISO project, cited to its source row", "the as-reported application status of each CAISO project (Active / Completed / Withdrawn), kept verbatim by tab", "each project's deliverability status (Full Capacity / Partial Capacity / Energy Only), TPD allocation, and cluster (study process), as CAISO reports it", "the count of projects in a scope (active vs completed vs withdrawn \u2014 by filtering application_status)" ], "current_sources": [ "energy.caiso.queue" ], "id": "power.interconnection_queue_caiso", "primitive": "query_power_interconnection_queue_caiso_v1", "product_spec": "blocks/power_interconnection_queue_caiso/card.md", "represented_facts": [ "CAISO's Public Queue Report reports each project's REQUESTED interconnection capacity (Net MWs to Grid) \u2014 a request, not built capacity \u2014 across the Active, Completed, and Withdrawn lifecycle tabs", "CAISO's queue reports each project's location (state, county), the Type/Fuel/MW hybrid triplets, the three-valued deliverability status (Full Capacity / Partial Capacity / Energy Only) with TPD allocation, the cluster study process, the per-phase study statuses, and lifecycle dates", "CAISO carries the requested-vs-built distinction in application_status + the lifecycle tab \u2014 a COMPLETED project carries an actual_online_date (the realized in-service date); CAISO publishes no separate built-MW column" ], "status": "available", "title": "Power Interconnection Queue (CAISO)" }, { "anchors": [ "state", "county_fips" ], "answers": [ "which projects have requested to connect to the NYISO grid, by state/county, fuel/technology, zone, and status", "the summer-peak (sp_mw) and winter-peak (wp_mw) megawatts of each queued NYISO project, cited to its source row", "NYISO load interconnection requests (the Load Projects tab) with their peak_mw_load, served as-reported", "the as-reported lifecycle status of each NYISO project (active / withdrawn / in-service / affected-system), kept by tab", "the as-reported study-phase code (study_status_code) and which studies are available, as NYISO reports them", "NYISO's own End-Use class per load request (end_use, 2026-07 edition onward, e.g. DAT / DAT-AI / DAT-CM, served verbatim) and the SIS study bundle (sis_bundle)", "the count of projects in a scope (active vs withdrawn vs in-service \u2014 by filtering application_status or sheet_name)" ], "current_sources": [ "energy.nyiso.queue" ], "id": "power.interconnection_queue_nyiso", "primitive": "query_power_interconnection_queue_nyiso_v1", "product_spec": "blocks/power_interconnection_queue_nyiso/card.md", "represented_facts": [ "NYISO's Interconnection Queue reports each project's REQUESTED interconnection capacity \u2014 summer (SP) and winter (WP) peak MW, kept separate \u2014 across every lifecycle tab NYISO publishes (nine through 2026-06; seven since the 2026-07 restructure folded the load/affected-system withdrawn lists into the active tabs under NYISO's own 0=Withdrawn code); a request, not built capacity", "NYISO uniquely publishes a Load Projects tab \u2014 load interconnection requests with their own peak_mw_load, and (since 2026-07) NYISO's own End-Use class per request (end_use, e.g. DAT / DAT-AI / DAT-CM, served verbatim \u2014 NYISO publishes no key for these codes) plus the SIS Bundle study-batch code (sis_bundle)", "NYISO carries the requested-vs-built distinction in application_status (the lifecycle tab's reading, overridden to the withdrawn form on NYISO's own status code 0) + study_status_code; the In Service tab is the built reading, and a project may appear on more than one tab (grain = sheet + queue_position)" ], "status": "available", "title": "Power Interconnection Queue (NYISO)" }, { "anchors": [ "state", "county_fips" ], "answers": [ "which projects have requested to connect to the ISO-NE grid, by state/county, fuel/technology, zone, and status", "the net / summer-peak / winter-peak megawatts of each queued ISO-NE project, cited to its source row", "the as-reported lifecycle status of each project (A=Active / C=Commercial / W=Withdrawn), kept separate from build-progress project_status", "the build-progress project_status (Under Study / Under Construction / In Service / \u2026), as ISO-NE reports it, never collapsed into application_status", "the request type (G=Generation / ETU=Elective Transmission Upgrade / TS=Transmission Service) and per-stage study statuses, as ISO-NE reports them", "the count of projects in a scope (active vs commercial vs withdrawn \u2014 by filtering application_status)" ], "current_sources": [ "energy.isone.queue" ], "id": "power.interconnection_queue_isone", "primitive": "query_power_interconnection_queue_isone_v1", "product_spec": "blocks/power_interconnection_queue_isone/card.md", "represented_facts": [ "ISO-NE's IRTT public-queue report lists each project's REQUESTED interconnection capacity \u2014 net, summer-peak and winter-peak MW, kept separate \u2014 for generation, elective-transmission-upgrade and transmission-service requests; a request, not built capacity", "ISO-NE carries the requested-vs-built distinction in application_status (A=Active / C=Commercial / W=Withdrawn) and a SEPARATE build-progress project_status (Under Study / Under Construction / In Service / \u2026), never collapsed; a Commercial project is the built reading", "ISO-NE publishes no load/data-center request type (all rows are generation or transmission); the queue-position (QP) is a non-unique reference reused across historical projects, so the grain is the published row ordinal" ], "status": "available", "title": "Power Interconnection Queue (ISO-NE)" }, { "anchors": [ "state", "county_fips" ], "answers": [ "which generation projects have requested to connect to the ERCOT (Texas) grid, by county, fuel, technology, CDR reporting zone, lifecycle, and size", "the requested capacity (MW) of each queued ERCOT project, cited to its source row", "the as-reported lifecycle of each project (ACTIVE / INACTIVE / CANCELLED, derived from ERCOT's own sheet structure), kept separate from build progress", "the build-progress signal \u2014 the GIM Study Phase token string and the milestone dates (screening study, FIS, IA signed, construction, energization), as ERCOT reports them", "the count of projects in a scope (active vs inactive vs cancelled \u2014 by filtering application_status)" ], "current_sources": [ "energy.ercot.queue" ], "id": "power.interconnection_queue_ercot", "primitive": "query_power_interconnection_queue_ercot_v1", "product_spec": "blocks/power_interconnection_queue_ercot/card.md", "represented_facts": [ "ERCOT's GIS Report lists each generation project's REQUESTED interconnection capacity (capacity_mw \u2014 one figure, no summer/winter split) across four lifecycle sheets (Large/Small Gen active, plus Inactive and Cancellation); a request, not built capacity", "ERCOT publishes no status column, so application_status (ACTIVE / INACTIVE / CANCELLED) is derived from the sheet the project is filed on (sheet_name served verbatim), and the build-progress reading is carried SEPARATELY in gim_study_phase + the milestone dates, never collapsed", "ERCOT files a hybrid project's legs as separate INR rows linked only by a shared poi_location (no in-row hybrid encoding); the GIS Report is generation-only and reports no load/data-center type" ], "status": "available", "title": "Power Interconnection Queue (ERCOT)" }, { "anchors": [ "state", "county_fips" ], "answers": [ "which generation projects have requested to connect to the SPP grid, by state, county, generation type, fuel, study cluster, transmission owner, and status", "the requested capacity (MW) of each queued SPP project, cited to its source row (and the five other MW columns SPP publishes, each labeled and never blended)", "the as-reported SPP status of each project (SPP's own vocabulary, kept verbatim with a per-source codebook), so an agent can scope to active vs withdrawn vs terminated", "the study cluster (DISIS-YYYY-NNN / Surplus / RTOE Transitional) and SPP regional cluster group, as SPP reports them", "the count of projects in a scope (by filtering native_status, state, generation_type, \u2026)" ], "current_sources": [ "energy.spp.queue" ], "id": "power.interconnection_queue_spp", "primitive": "query_power_interconnection_queue_spp_v1", "product_spec": "blocks/power_interconnection_queue_spp/card.md", "represented_facts": [ "SPP's GI Summary lists each generation project's REQUESTED interconnection capacity (capacity_mw \u2014 SPP's headline figure, with five other labeled MW columns served and never blended); a request, not built capacity", "SPP publishes a native Status column whose vocabulary it controls, so native_status is served VERBATIM with a codebook (never mapped to a lifecycle enum); ~66% of rows are WITHDRAWN, so a total is scoped by native_status, never read as built", "SPP spans ~14 central-US states (state is a real anchor), carries only a free-text town-or-county (county_fips derived by name where it resolves, else null), encodes hybrids natively as a Hybrid generation_type (no is_hybrid invented), and is generation-only (no load/data-center type)" ], "status": "available", "title": "Power Interconnection Queue (SPP)" }, { "anchors": [ "state" ], "answers": [ "the day-ahead wholesale price ($/MWh) at an ERCOT settlement point for a given delivery day and hour, cited to its source row", "the price at a named hub (e.g. HB_NORTH, HB_HOUSTON) or load zone (e.g. LZ_HOUSTON) \u2014 the regional benchmark prices", "the daily price shape at a settlement point (the 24 hourly day-ahead prices), and average / minimum / maximum price over a window", "how a settlement point is classified by ERCOT (Hub / Load Zone / Resource Node / DC-tie, as ERCOT's own verbatim code), so a single-plant node is not mistaken for a regional benchmark", "the price spread across settlement points or types for a given hour or day" ], "current_sources": [ "energy.ercot.prices" ], "id": "power.price_ercot", "primitive": "query_power_price_ercot_v1", "product_spec": "blocks/power_price_ercot/card.md", "represented_facts": [ "ERCOT's Day-Ahead Market Settlement Point Prices (NP4-190-CD) \u2014 the price ($/MWh) cleared the day before each operating day at every ERCOT settlement point, served hourly and point by point as a TOTAL (no energy/congestion/loss split; none is synthesized)", "a price is intensive ($/MWh): it is averaged / min'd / max'd over a scope, never summed; ERCOT's own hour-ending label and DST flag are carried verbatim (24 hours normally, 25 on the fall-back date, 23 on spring-forward)", "settlement_point_type is ERCOT's OWN verbatim classification (HU hub / LZ load zone / RN resource node / DC-tie \u2026), joined from ERCOT's published settlement-points list and never collapsed; a settlement point is electrical/aggregate, not a plant \u2014 the only geography anchor is state = TX", "historical delivery coverage begins 2014-05-02 from ERCOT's Data Access Portal archives; settlement-point names remain exactly as published in each vintage, and an older name absent from the current type reference receives a null type rather than a rewrite or guess" ], "status": "available", "title": "Power Prices (ERCOT day-ahead)" }, { "anchors": [], "answers": [ "PJM's cited marginal ELCC accreditation fraction for a resource class in a named auction document", "how preliminary-outlook ratings differ from final-auction or incremental-auction ratings without reconciling them", "all PJM resource classes in a linked class-ratings table, with the verbatim class name and normalized family" ], "current_sources": [ "energy.pjm.elcc" ], "id": "power.capacity_accreditation_pjm", "primitive": "query_power_capacity_accreditation_pjm_v1", "product_spec": "blocks/power_capacity_accreditation_pjm/card.md", "represented_facts": [ "PJM-published marginal Effective Load Carrying Capability (ELCC) class ratings, as a fraction of nameplate capacity, for each resource class and delivery year in each linked final Base Residual Auction document, Incremental Auction document, or preliminary multi-year outlook. Document identity is a dimension: preliminary and final ratings for the same delivery year are separate cited atoms and are never merged, preferred, reconciled, or corrected by this block." ], "status": "available", "title": "PJM ELCC Class Ratings (internal)" }, { "anchors": [], "answers": [ "RTO-wide and separated-LDA UCAP capacity-market clearing prices for a named PJM delivery year", "cleared RTO UCAP MW and the report-stated RTO reliability requirement where published", "the administrative price cap and floor as each stating document publishes them, making a cap-bound clearing visible", "for auctions with no stated collar, which documents were searched, so a None cap is provably not-stated", "documented coverage from delivery year 2018/2019 onward, with unsupported source formats recorded as exceptions" ], "current_sources": [ "energy.pjm.capacity_market" ], "id": "power.capacity_market_pjm", "primitive": "query_power_capacity_market_pjm_v1", "product_spec": "blocks/power_capacity_market_pjm/card.md", "represented_facts": [ "PJM Reliability Pricing Model Base Residual Auction results: UCAP-basis resource clearing prices in USD per MW-day for the RTO and published LDAs, RTO cleared UCAP MW, the stated RTO reliability requirement, and any administrative price cap and floor stated in the auction results report or the planning-period-parameters workbook \u2014 each on the basis its stating document uses, quoted verbatim in cap_basis. Documents searched for a collar that state none yield a collar_search atom, so absence is provably \"not stated\", never \"not parsed\". Workbook and report facts remain separate cited atoms at their exact source coordinates." ], "status": "available", "title": "PJM RPM Capacity-Market Results (internal)" } ], "id": "power" }, { "capabilities": [ { "anchors": [], "answers": [ "monthly private data-center construction spending ($ millions), seasonally-adjusted annual rate or not-adjusted monthly level (cited to the source cell)", "monthly private computer/electronic/electrical (semiconductor-fab) construction spending ($ millions)", "the data-center vs fab construction-spending trend over time (each as its own per-month series)", "whether a given month's value is preliminary, revised, or final (the Census revision status, carried verbatim)" ], "current_sources": [ "construction.census.c30_vip" ], "id": "ai_infrastructure.construction", "primitive": "query_ai_infrastructure_construction_v1", "product_spec": "blocks/ai_infrastructure_construction/card.md", "represented_facts": [ "Census C30 (Value of Construction Put in Place) reports the monthly value of private DATA-CENTER construction put in place ($ millions), served both seasonally-adjusted (annual rate) and not-seasonally-adjusted (monthly level), verbatim and cited", "Census C30 reports the monthly value of private COMPUTER/ELECTRONIC/ELECTRICAL (semiconductor-fab) construction put in place ($ millions) on the same two bases" ], "status": "available", "title": "AI Infrastructure Construction (data centers + fabs)" }, { "anchors": [ "state", "county_fips" ], "answers": [ "quarterly data-center-industry (NAICS 518210) employment, establishments, and wages by US / state / county", "quarterly semiconductor-manufacturing (NAICS 334413) employment and wages by US / state / county", "the state/county geography of data-center and semiconductor employment since 2014 (e.g. Loudoun County, VA)", "TOTAL covered employment and wages for any US county, quarterly since 2014 (\"did the county's employment rise?\")", "county construction-sector (NAICS 23) and commercial-building (236220) employment \u2014 the buildout-phase series", "county retail (\"44-45\"), accommodation (721), and food-service (722) employment \u2014 the induced local-economy series", "whether a county x industry cell is disclosed or withheld (the disclosure_code, carried verbatim)" ], "current_sources": [ "employment.bls.qcew" ], "id": "ai_infrastructure.employment", "primitive": "query_ai_infrastructure_employment_v1", "product_spec": "blocks/ai_infrastructure_employment/card.md", "represented_facts": [ "BLS QCEW reports quarterly establishments, monthly employment, and quarterly wages for the data-center industry (NAICS 518210, computing infrastructure / data processing / web hosting) by national / state / county and ownership, served verbatim and cited", "BLS QCEW reports the same for semiconductor & related device manufacturing (NAICS 334413); a confidential county \u00d7 industry cell is served as absent (withheld), never as a measured zero", "BLS QCEW reports the same for the place-based local-economy series (PD-069): total all industries ('10'), construction (23), commercial & institutional building construction (236220), retail trade ('44-45'), accommodation (721), and food services (722) \u2014 what a facility buildout does to a county's whole economy; jobs count at the employer's establishment, not the work site" ], "status": "available", "title": "AI Infrastructure Employment (data centers + semiconductors)" }, { "anchors": [], "answers": [ "monthly U.S. import value (USD) of all integrated circuits \u2014 HS-8542 \u2014 cited to the source row", "chip imports by country of origin (e.g. Taiwan, Malaysia, South Korea, Israel) \u2014 supply-source concentration", "the U.S. chip-import trend over time (each country / grouping / the national total as its own monthly series)", "general imports value vs imports-for-consumption value at the same grain" ], "current_sources": [ "trade.census.intltrade_imports_hs" ], "id": "ai_infrastructure.trade", "primitive": "query_ai_infrastructure_trade_v1", "product_spec": "blocks/ai_infrastructure_trade/card.md", "represented_facts": [ "Census International Trade reports the monthly customs value (USD) of U.S. imports of HS-8542 'Electronic integrated circuits' \u2014 ALL integrated circuits (processors, memory, amplifiers, parts), not AI-accelerator-specific \u2014 by country of origin, as general imports and imports-for-consumption value, served verbatim and cited", "Census reports these imports across overlapping country GROUPINGS (ASIA, APEC, EU, OECD, ASEAN, the continents) and an all-countries TOTAL; the groupings overlap each other and the countries, so they are never summed \u2014 the served TOTAL is the only national figure" ], "status": "available", "title": "AI Infrastructure Trade (chip imports)" }, { "anchors": [], "answers": [ "monthly U.S. import value (USD) of semiconductor-manufacturing equipment \u2014 HS-8486 \u2014 cited to the source row", "equipment imports by country of origin (e.g. Japan, the Netherlands, South Korea, Singapore) \u2014 tool-supply concentration", "the fab-buildout TOOLING trend \u2014 equipment flowing in between construction (C30) and chip output (HS-8542)", "general imports value vs imports-for-consumption value at the same grain" ], "current_sources": [ "trade.census.intltrade_equipment_hs" ], "id": "ai_infrastructure.equipment_trade", "primitive": "query_ai_infrastructure_equipment_trade_v1", "product_spec": "blocks/ai_infrastructure_equipment_trade/card.md", "represented_facts": [ "Census International Trade reports the monthly customs value (USD) of U.S. imports of HS-8486 'Machines and apparatus for the manufacture of semiconductor boules/wafers, devices, integrated circuits or flat panel displays' \u2014 the chip-MAKING equipment (which includes flat-panel-display machinery), NOT the chips themselves \u2014 by country of origin, as general imports and imports-for-consumption value, served verbatim and cited", "Census reports these imports across overlapping country GROUPINGS (ASIA, APEC, EU, OECD, ASEAN, the continents) and an all-countries TOTAL; the groupings overlap each other and the countries, so they are never summed \u2014 the served TOTAL is the only national figure" ], "status": "available", "title": "AI Infrastructure Equipment Trade (chip-making tools)" }, { "anchors": [], "answers": [ "the monthly industrial-production index (2017=100) for semiconductor & other electronic component manufacturing (NAICS 3344), seasonally adjusted or not adjusted, cited to the Fed's source observation", "monthly capacity utilization (percent, seasonally adjusted) for the same industry \u2014 how hot the domestic fabs and component plants are running", "the monthly capacity index (2017=100) behind the utilization rate", "the production / utilization trend over time (each series as its own per-month reading, averaged \u2014 never summed \u2014 over windows)" ], "current_sources": [ "production.fed.g17" ], "id": "ai_infrastructure.production", "primitive": "query_ai_infrastructure_production_v1", "product_spec": "blocks/ai_infrastructure_production/card.md", "represented_facts": [ "Fed G.17 reports the monthly industrial-production index (2017=100, seasonally adjusted and not adjusted) for semiconductor and other electronic component manufacturing (NAICS 3344) \u2014 the finest split G.17 publishes for this family, served verbatim and cited to the Board's SDMX observation", "Fed G.17 reports monthly capacity utilization (percent) and the capacity index (2017=100) for the same industry, seasonally adjusted only; an index or a rate is intensive \u2014 averaged over a window, never summed" ], "status": "available", "title": "AI Infrastructure Production (semiconductor output and utilization)" } ], "id": "ai_infrastructure" }, { "capabilities": [ { "anchors": [], "answers": [ "monthly U.S. imports of industrial robots in DOLLARS and in UNITS (robot counts) \u2014 cited to the source row", "robot imports by country of origin (e.g. Japan, China, South Korea, Germany, Mexico) \u2014 supply concentration", "the two robot categories separately \u2014 multipurpose robots (8479.50) vs lifting/handling robots (8428.70)", "general imports vs imports-for-consumption at the same grain, value and units" ], "current_sources": [ "trade.census.intltrade_robotics_hs" ], "id": "robotics.trade", "primitive": "query_robotics_trade_v1", "product_spec": "blocks/robotics_trade/card.md", "represented_facts": [ "Census International Trade reports the monthly customs value (USD) AND unit count (number of robots) of U.S. imports of industrial robots \u2014 HS-10 8479500000 'INDUSTRIAL ROBOTS, NESOI' (multipurpose) and 8428700000 'INDUSTRIAL ROBOTS FOR LIFTING, HANDLING, LOADING OR UNLOADING' (created by HS 2022; no data before 2022-01) \u2014 by country of origin, as general imports and imports-for-consumption, served verbatim and cited", "Census reports these imports across overlapping country GROUPINGS (ASIA, APEC, EU, OECD, ASEAN, the continents) and an all-countries TOTAL; the groupings overlap each other and the countries, so they are never summed \u2014 the served TOTAL is the only national figure" ], "status": "available", "title": "Robotics Trade (industrial-robot imports, value + robot counts)" }, { "anchors": [ "state" ], "answers": [ "what share of US manufacturing plants use industrial robots \u2014 nationally, by state, by industry (NAICS), by plant size \u2014 the only official installed-base adoption series", "what share of manufacturing employees work at plants with robots, at the same grains", "robotics capital expenditures ($1000) by industry, state, and plant size", "how adoption differs across plant sizes (small plants barely automate; large plants dominate)", "each edition separately (ASM 2018-2021 annual series; EC 2022 census snapshot), with the coverage break between them named, never spliced" ], "current_sources": [ "robotics.census.robotic_equipment" ], "id": "robotics.adoption", "primitive": "query_robotics_adoption_v1", "product_spec": "blocks/robotics_adoption/card.md", "represented_facts": [ "The Census Industrial Robotic Equipment product (experimental \u2014 the first official federal robotics-adoption statistics) reports the percent of manufacturing plants with industrial robots, the percent of manufacturing employees at plants with robots, and robotics capital expenditures ($1000) by NAICS industry, state, and plant size, in two editions (ASM 2018-2021 and the 2022 Economic Census), served verbatim and cited to the exact workbook cell-group", "The two editions measure different coverage universes (the 2022 Economic Census reaches small plants the ASM sample does not \u2014 US plants-with-robots 12.1% ASM-2021 vs 6.4% EC-2022), so editions are compared, never spliced into one series (PD-066)" ], "status": "available", "title": "Robotics Adoption (share of plants using robots, workers exposed, robotics capex)" } ], "id": "robotics" }, { "capabilities": [ { "anchors": [ "state" ], "answers": [ "every FCC space-station filing on record \u2014 by applicant, application type, status, and filing date \u2014 each cited to its exact record in the FCC's own database dump", "the licensing trail of any satellite system or operator (e.g. every SpaceX / Intelsat / Kuiper filing), with the FCC's own description text", "where each filing stands now (the FCC's own status vocabulary, decoded from the same dump vintage) \u2014 granted, pending, dismissed, surrendered \u2014 updated daily", "filing counts by applicant, type, status, state (applicant address), or period \u2014 the satellite-buildout pipeline signal back to the 1960s", "the lifecycle dates of any filing (filed, granted, expires, \u2026), e.g. when an authorization expires" ], "current_sources": [ "space.fcc.ibfs_sat" ], "id": "space.satellite_filings", "primitive": "query_space_satellite_filings_v1", "product_spec": "blocks/space_satellite_filings/card.md", "represented_facts": [ "The FCC's IBFS daily bulk database dump records every space-station (SAT-subsystem) filing in the FCC satellite licensing docket back to the 1960s \u2014 file number, call sign, application type and status in the FCC's own vocabulary (verbatim codes plus the FCC's own decode text from the same dump vintage), the full lifecycle date family, the FCC's plain-English description, and the applicant identity joined by the source's own address_key \u2014 served as-reported and cited to the exact record", "New-filing intake into IBFS structurally ended at the FCC's ICFS system cutover (~mid-2025; measured: zero 2026-filed records while 2026-dated status actions continue daily), and ICFS publishes no bulk data \u2014 so filings submitted after the cutover are not in this source (PD-064, engraved as a refusal)" ], "status": "available", "title": "Space Satellite Filings (FCC satellite licensing docket)" } ], "id": "space" } ], "version": "v1" }, "tool": "list_capabilities_v1" }, { "params": {}, "result": { "anchors": [ { "about": "2-letter state/jurisdiction code (PD-003).", "format": "usps_state", "kind": "geography", "name": "state", "scope": "universal" }, { "about": "5-digit Census county FIPS, zero-padded string.", "format": "fips5", "kind": "geography", "name": "county_fips", "scope": "universal" } ], "capability": "power.interconnection_queue_spp", "codebooks": { "cluster_group": { "codes": {}, "coverage": "the distinct cluster groups served from the SPP snapshot", "note": "SPP's regional cluster group, e.g. `01 NORTH`, `02 NEBRASKA`, `03 CENTRAL`, `04 SOUTHEAST`, `05 SOUTHWEST`. Filter by SPP's EXACT value.", "semantics": "as_reported_spp_cluster_group", "source": "SPP GI Summary `Cluster Group` column \u2014 SPP's regional grouping." }, "current_cluster": { "codes": {}, "coverage": "the distinct clusters served from the SPP snapshot", "note": "SPP's study cluster, e.g. `DISIS-2024-001`, `Surplus`, `RTOE Transitional Cluster` (blank for un-clustered rows). Filter by SPP's EXACT value.", "semantics": "as_reported_spp_cluster", "source": "SPP GI Summary `Current Cluster` column \u2014 SPP's study-cluster identifier." }, "fuel_type": { "codes": {}, "coverage": "the distinct fuel-type strings served from the SPP snapshot", "note": "Free-text and often blank; slash-delimited combos (e.g. `Solar/Storage`, `Wind/Storage`) are kept WHOLE, never split. Filter by SPP's EXACT string.", "semantics": "as_reported_spp_fuel_type", "source": "SPP GI Summary `Fuel Type` column \u2014 free-text, often slash-delimited for hybrids." }, "generation_type": { "codes": {}, "coverage": "the distinct generation types served from the SPP snapshot", "note": "SPP's own values, served verbatim \u2014 e.g. `Wind`, `Solar`, `Battery/Storage`, `Thermal`, `Hybrid`, `Hydro`. SPP encodes hybrids NATIVELY as `Hybrid` (no is_hybrid is invented). SPP's own case inconsistencies (`WIND`/`wind` vs `Wind`) are surfaced as-reported, not normalized. Filter by SPP's EXACT value.", "semantics": "as_reported_spp_generation_type", "source": "SPP GI Summary `Generation Type` column \u2014 SPP's own technology grouping." }, "native_status": { "codes": { "DISIS STAGE": { "label": "In a Definitive Interconnection System Impact Study cluster" }, "ERAS": { "label": "Expedited Resource Adequacy Study" }, "FACILITY STUDY STAGE": { "label": "In the facility study stage" }, "IA FULLY EXECUTED/COMMERCIAL OPERATION": { "label": "IA signed, in commercial operation" }, "IA FULLY EXECUTED/ON SCHEDULE": { "label": "Interconnection Agreement signed, on schedule" }, "IA FULLY EXECUTED/ON SUSPENSION": { "label": "IA signed, suspended" }, "IA PENDING": { "label": "Interconnection Agreement not yet executed" }, "ICS": { "label": "as-reported SPP value (rare)" }, "None": { "label": "literal 'None' string as SPP publishes it (rare)" }, "SPECIAL STUDY": { "label": "In a special study" }, "TERMINATED": { "label": "Terminated \u2014 left the queue" }, "WITHDRAWN": { "label": "Withdrawn \u2014 left the queue (the dominant class, ~66%)" } }, "coverage": "the status values observed in the SPP snapshot (live; SPP may add more)", "note": "ALWAYS scope by `native_status`. Served VERBATIM (never mapped to a lifecycle enum, never a derived active/withdrawn boolean \u2014 that equivalence is the analyst's). ~66% of rows are `WITHDRAWN`. A queue-MW total is REQUESTED capacity, never built \u2014 for built/operating capacity use query_power_capacity_v1. Filter by SPP's EXACT string.", "semantics": "as_reported_spp_status", "source": "SPP GI Summary `Status` column \u2014 SPP's OWN verbatim status vocabulary." }, "service_type": { "codes": {}, "coverage": "the distinct service types served from the SPP snapshot", "note": "SPP's request service type, e.g. `ER/NR` (Energy Resource / Network Resource), `ER`, `NR`. Filter by SPP's EXACT value.", "semantics": "as_reported_spp_service_type", "source": "SPP GI Summary `Service Type` column." } }, "data_point": { "does_not_answer": [ "built/operating/nameplate capacity as a queue total (the MW columns are REQUESTED interconnection, not built; for operating capacity use power.capacity / EIA-860M)", "a single nameplate figure (SPP publishes six MW columns \u2014 capacity, max summer, max winter, requested max injection, requested network resource deliverability, nameplate \u2014 all served and never collapsed)", "a sum of MW treated as planned or operating capacity (most queued MW withdraws \u2014 ~66% of SPP rows are WITHDRAWN \u2014 totals are scoped by native_status, never read as built)", "a cross-ISO or national queue total (methodologies, inclusion, and withdrawal rates differ per ISO \u2014 never summed or deduped across ISOs; for MISO use query_power_interconnection_queue_v1, for PJM query_power_interconnection_queue_pjm_v1 (or query_power_interconnection_queue_pjm_cycle_v1), for CAISO query_power_interconnection_queue_caiso_v1, for NYISO query_power_interconnection_queue_nyiso_v1, for ISO-NE query_power_interconnection_queue_isone_v1, for ERCOT query_power_interconnection_queue_ercot_v1)", "which projects are \"data-center driven\" or load requests (SPP's GI queue publishes no load/data-center request type \u2014 it is generation-only; that inference is the analyst's, never tagged here)", "the probability that a queued project will actually be built or reach commercial operation", "generation MWh, demand, prices, retail sales, or transmission flows", "lat/lon or plant-level attribution (SPP supplies no coordinate; only a free-text town-or-county, the State column, and derived county_fips)", "queues for other ISOs/RTOs (MISO, PJM, CAISO, NYISO, ISO-NE, ERCOT) \u2014 each is a separate block under the same gate" ], "grain": "project_snapshot", "id": "power.interconnection_queue_spp", "note": "This is SPP's interconnection queue \u2014 Southwest Power Pool's public GI Summary report. `capacity_mw` is REQUESTED interconnection capacity (a waiting line), NOT built / installed / operating capacity (SPP also publishes five other MW columns \u2014 summer/winter peak, requested injection/NRD, nameplate \u2014 served labeled, never blended). Always scope by `native_status` \u2014 SPP's OWN verbatim vocabulary (e.g. `IA FULLY EXECUTED/ON SCHEDULE`, `DISIS STAGE`, `IA PENDING`, `WITHDRAWN`, `TERMINATED`), served as-reported and never mapped to a lifecycle enum; ~66% of rows are WITHDRAWN. For operating capacity use query_power_capacity_v1. SPP is generation-only and infers no load/data-center type. SPP keeps no per-vintage archive, so this serves a CURRENT snapshot (history accrues forward, not deep as_of time-travel). SPP only \u2014 never summed or compared across ISOs; for MISO use query_power_interconnection_queue_v1, for PJM query_power_interconnection_queue_pjm_v1 (or query_power_interconnection_queue_pjm_cycle_v1), for CAISO query_power_interconnection_queue_caiso_v1, for NYISO query_power_interconnection_queue_nyiso_v1, for ISO-NE query_power_interconnection_queue_isone_v1, for ERCOT query_power_interconnection_queue_ercot_v1.", "product_spec": "blocks/power_interconnection_queue_spp/card.md", "represented_fact": "The SPP generator interconnection queue \u2014 Southwest Power Pool's public GI Summary report, the waiting line of every generation project that has REQUESTED to connect to the SPP grid (the ~14-state central-US RTO), served as-reported, project by project. SPP's full published structure is carried faithfully, in SPP's own words, across all 27 columns of the report: the six labeled megawatt readings (`capacity_mw`, `max_summer_mw`, `max_winter_mw`, `requested_max_injection_mw`, `requested_nrd_mw`, `nameplate_capacity_mw`, kept SEPARATE \u2014 SPP publishes several and we never blend them), the as-reported `native_status` (SPP's own vocabulary \u2014 WITHDRAWN, IA FULLY EXECUTED/ON SCHEDULE, IA FULLY EXECUTED/COMMERCIAL OPERATION, DISIS STAGE, IA PENDING, SPECIAL STUDY, TERMINATED, FACILITY STUDY STAGE, ERAS, IA FULLY EXECUTED/ON SUSPENSION, \u2026, kept verbatim with a per-source codebook, never mapped to a lifecycle enum), the `generation_type` and free-text `fuel_type` (kept verbatim, including SPP's own `Hybrid` generation type and slash-delimited fuel combos \u2014 no is-hybrid flag is invented), the study `current_cluster` (DISIS-YYYY-NNN / Surplus / RTOE Transitional \u2026) and SPP regional `cluster_group`, the transmission owner at the point of interconnection (`to_at_poi`), the `service_type`, the substation, and the lifecycle dates (request received, in-service, commercial operation, withdrawn, cessation). This is a REQUEST, not built capacity: historically the large majority of queued MW withdraws before it is built (in the SPP file, ~66% of rows are WITHDRAWN). This is a forward-looking slice (capacity/generation/demand are backward-looking actuals). SPP genuinely spans many states, so `state` is a real dimension and anchor; SPP carries no county_fips and no lat/lon, only a free-text \"Nearest Town or County\" \u2014 `county_fips` is derived by name where it resolves and left null otherwise (towns, multi-county labels, and unresolved names stay null, never guessed \u2014 the derivation is LOSSY by design). The grain key is SPP's Generation Interconnection Number (globally unique). SPP publishes no load/data-center request type \u2014 the queue is generation-only \u2014 so no load or data-center signal is inferred; that interpretation is the analyst's. SPP keeps no per-vintage archive (the CSV is regenerated on demand), so history accrues forward from first capture \u2014 this serves a CURRENT snapshot, not deep as_of time-travel.", "source_basis": [ "energy.spp.queue" ], "source_decisions": [ "docs/sources/energy/spp/gi_queue/build-plan.md" ] }, "input": { "controls": [ "include_records", "include_evidence", "limit", "order_by", "top_n", "order", "rollup_other" ], "date_range_params": [ "request_received_from", "request_received_to", "commercial_operation_date_from", "commercial_operation_date_to" ], "date_ranges": [ "request_received", "commercial_operation_date" ], "field_metadata": {}, "filters": [ "as_of", "state", "county_fips", "native_status", "generation_type", "fuel_type", "service_type", "current_cluster", "cluster_group", "to_at_poi", "request_received", "commercial_operation_date" ], "group_by": [ "state", "county_fips", "native_status", "generation_type", "fuel_type", "service_type", "current_cluster", "cluster_group", "to_at_poi" ], "ranking": { "no_ranking": "Omit order_by and top_n to return all groups in group-key order.", "order": { "default": "desc", "valid_values": [ "desc", "asc" ] }, "order_by": { "accepts": "one of output.metrics", "note": "Ranks the groups by a metric (a measure). Not a group_by dimension \u2014 rows already come back grouped by each group_by field.", "requires": [ "group_by" ], "valid_values": [ "capacity_mw", "source_record_count" ] }, "top_n": { "note": "Keeps the top N groups by order_by; the rest fold into one (other) remainder (additive metrics sum into it, non-additive ones are nulled) so the result still reconciles to summary.totals.", "requires": [ "group_by", "order_by" ], "type": "positive integer" } } }, "output": { "aggregate_citation_fields": [ "source_id", "publisher", "source_url", "source_file", "raw_file_sha256", "as_of", "source_rows_count", "source_rows_sample", "verify", "lineage_filter" ], "citation_fields": [ "source_id", "source_url", "source_file", "sheet", "source_row", "raw_file_sha256", "as_of" ], "detail_fields": [ "source_id", "iso", "generation_interconnection_number", "source_record_key", "native_status", "state", "state_raw", "nearest_town_or_county", "county_fips", "county_fips_source", "county_fips_unresolved", "ifs_queue_number", "current_cluster", "cluster_group", "to_at_poi", "service_type", "generation_type", "fuel_type", "substation_or_line", "jtiq_participant", "jtiq_commitment", "cause_of_delay", "capacity_mw", "max_summer_mw", "max_winter_mw", "requested_max_injection_mw", "requested_nrd_mw", "nameplate_capacity_mw", "in_service_date", "commercial_operation_date", "cessation_date", "original_generator_commercial_op_date", "request_received", "date_withdrawn", "report_period", "source_row_number", "as_of", "raw_file_sha256", "citation" ], "metric_groups": { "records": [ "source_record_count" ], "requested_mw": [ "capacity_mw" ] }, "metric_metadata": { "capacity_mw": { "additive_across_groups": true, "aggregation": "sum", "authoritative_total_path": "summary.totals.capacity_mw", "category": "requested_mw", "definition": "The project's requested interconnection capacity in MW, as SPP reports it (the `Capacity` column \u2014 SPP's headline MW figure).", "description": "This is REQUESTED interconnection capacity (a project in the queue), NOT built, installed, or operating capacity: historically the large majority of queued MW withdraws before it is built (~66% of SPP rows are WITHDRAWN). It is additive across distinct rows (each is its own request) but must be read as REQUESTED \u2014 scope it with `native_status` (SPP's own verbatim vocabulary). `capacity_mw` is SPP's headline `Capacity` figure; SPP publishes five other MW columns (`max_summer_mw`, `max_winter_mw`, `requested_max_injection_mw`, `requested_nrd_mw`, `nameplate_capacity_mw`) served labeled in the detail records and never blended. For operating capacity use query_power_capacity_v1.", "display_name": "Capacity (MW, requested)", "display_precision": "MW values are rounded to 6 decimal places in JSON to remove binary floating-point noise.", "grain": "queue project row", "null_handling": "capacity_mw=0 is a REAL value, not missing. A row with no reported value contributes null (ignored by the sum). An empty-query summary returns zero.", "rollup_behavior": "additive_partition_metric", "row_metric_path": "rows[].metrics.capacity_mw", "source_fields": [ "Capacity" ], "unit": "MW" }, "source_record_count": { "additive_across_groups": true, "aggregation": "count source records", "authoritative_total_path": "summary.totals.source_record_count", "category": "records", "definition": "Count of SPP GI queue rows in the current result scope (one atom = one project row).", "description": "Number of queued rows contributing to the value \u2014 scope with native_status to separate active from withdrawn from terminated.", "display_name": "Queued row count", "display_precision": "Integer.", "grain": "queue project row", "null_handling": "Always an integer count.", "rollup_behavior": "additive_partition_metric", "row_metric_path": "rows[].metrics.source_record_count", "source_fields": [ "source_record_key" ], "unit": "count" } }, "metrics": [ "capacity_mw", "source_record_count" ], "summary_fields": [ "group_count", "totals" ] }, "primitive": "query_power_interconnection_queue_spp_v1", "status": "available" }, "tool": "describe_power_interconnection_queue_spp_v1" }, { "params": { "include_records": true, "limit": 1, "native_status": "DISIS STAGE" }, "result": { "as_of": "2026-06-22", "citations": { "c1": { "source_rows_count": 157, "verify": { "as_of": "2026-06-22", "raw_file_sha256": "b7ee16555e89c6eee5ce7393e3129c74e5148ca72d0f85366ee80b53aed123f7", "sheet": "GI_Summary", "source_file": "spp-gi_2026-06-22_sample.csv", "source_id": "energy.spp.queue", "source_row": 37, "source_url": "https://opsportal.spp.org/Studies/GISummary" } } }, "primitive": "query_power_interconnection_queue_spp_v1", "query": { "as_of": "2026-06-22", "group_by": [], "include_records": true, "limit": 1, "native_status": [ "DISIS STAGE" ] }, "records": [ { "as_of": "2026-06-22", "capacity_mw": 150.0, "cause_of_delay": null, "cessation_date": null, "citation": { "as_of": "2026-06-22", "raw_file_sha256": "b7ee16555e89c6eee5ce7393e3129c74e5148ca72d0f85366ee80b53aed123f7", "sheet": "GI_Summary", "source_file": "spp-gi_2026-06-22_sample.csv", "source_id": "energy.spp.queue", "source_row": 37, "source_url": "https://opsportal.spp.org/Studies/GISummary" }, "cluster_group": null, "commercial_operation_date": "2028-06-01", "county_fips": null, "county_fips_source": null, "county_fips_unresolved": false, "current_cluster": "RTOE Transitional Cluster", "date_withdrawn": null, "fuel_type": null, "generation_interconnection_number": "GI-SISS-2026-04", "generation_type": "Battery/Storage", "ifs_queue_number": null, "in_service_date": "2028-01-03", "iso": "SPP", "jtiq_commitment": null, "jtiq_participant": null, "max_summer_mw": 150.0, "max_winter_mw": 150.0, "nameplate_capacity_mw": 0.0, "native_status": "DISIS STAGE", "nearest_town_or_county": "Kit Carson County,", "original_generator_commercial_op_date": null, "raw_file_sha256": "b7ee16555e89c6eee5ce7393e3129c74e5148ca72d0f85366ee80b53aed123f7", "report_period": "2026-06-22", "request_received": "2026-02-09", "requested_max_injection_mw": 0.0, "requested_nrd_mw": 0.0, "service_type": "ER", "source_id": "energy.spp.queue", "source_record_key": "GI-SISS-2026-04", "source_row_number": 37, "state": "CO", "state_raw": "CO", "substation_or_line": "Looff 230 Substation (Burlington\nExpansion)", "to_at_poi": "TSGT" } ], "rows": [ { "group": {}, "lineage": { "citation_ref": "c1" }, "metrics": { "capacity_mw": 43685.883, "source_record_count": 157 } } ], "source_id": "energy.spp.queue", "summary": { "group_count": 1, "totals": { "capacity_mw": 43685.883, "source_record_count": 157 } } }, "tool": "query_power_interconnection_queue_spp_v1" }, { "params": { "as_of": "2026-06-22", "raw_file_sha256": "b7ee16555e89c6eee5ce7393e3129c74e5148ca72d0f85366ee80b53aed123f7", "sheet": "GI_Summary", "source_file": "spp-gi_2026-06-22_sample.csv", "source_id": "energy.spp.queue", "source_row": 37, "source_url": "https://opsportal.spp.org/Studies/GISummary" }, "result": { "as_of": "2026-06-22", "cited_gin": "GI-SISS-2026-04", "hash_verified": true, "raw_file_sha256": "b7ee16555e89c6eee5ce7393e3129c74e5148ca72d0f85366ee80b53aed123f7", "row_values": { "capacity_mw": "150", "cause_of_delay": null, "cessation_date": null, "cluster_group": null, "commercial_operation_date": "6/1/2028", "current_cluster": "RTOE Transitional Cluster", "date_withdrawn": null, "fuel_type": null, "generation_interconnection_number": "GI-SISS-2026-04", "generation_type": "Battery/Storage", "ifs_queue_number": null, "in_service_date": "1/3/2028", "jtiq_commitment": null, "jtiq_participant": null, "max_summer_mw": "150", "max_winter_mw": "150", "nameplate_capacity_mw": "0", "native_status": "DISIS STAGE", "nearest_town_or_county": "Kit Carson County,", "original_generator_commercial_op_date": null, "request_received": "2/9/2026", "requested_max_injection_mw": "0", "requested_nrd_mw": "0", "service_type": "ER", "state_raw": "CO", "substation_or_line": "Looff 230 Substation (Burlington\nExpansion)", "to_at_poi": "TSGT" }, "sheet": "GI_Summary", "source_file": "spp-gi_2026-06-22_sample.csv", "source_id": "energy.spp.queue", "source_row": 37, "source_url": "https://opsportal.spp.org/Studies/GISummary" }, "tool": "get_source_evidence_v1" } ] }