PJM · Grid

PJM operations summary, projected RTO peak

PJM's morning projection of the day's peak for the whole RTO: the load forecast, the capacity scheduled against it, net interchange and the operating reserve left over — kept as vintages.

pjm-ops-peak-rtodaily, each morning · 1d rows1 entity

What is in it

Updates
daily, each morning · 1d rows
Entities
1 entity
Source timezone
US Eastern — every timestamp Dryos serves is UTC
Coverage
10 November 2026 to now
Rows held
16
Primary key
iso, interval_start_utc, source_published_at_utc

What it measures

Every value, its unit, and what the source means by it.

  • Peak load forecastMW

    Load forecast at the projected peak.

    load_forecast_mw
  • Scheduled capacityMW

    Internal scheduled capacity plus net tie flow plus adjustments.

    total_scheduled_capacity_mw
  • Operating reserveMW

    Scheduled capacity less the load forecast.

    operating_reserve_mw

Columns

Exactly what a request answers with, read from the API rather than written here.

ColumnTypeDescription
interval_start_utcrequiredtimestampStart of the interval, UTC, read from PJM's own UTC column.e.g. 2026-09-09T12:30:00Z
isorequiredstringPublishing ISO.e.g. PJM
load_forecast_mwnumberLoad forecast at the projected peak, MW.e.g. 92340
internal_scheduled_capacity_mwnumberGeneration scheduled inside PJM for the peak, MW.e.g. 118420
scheduled_tie_flow_mwnumberNet scheduled interchange at the peak, MW, as PJM signs it.e.g. -3120
capacity_adjustments_mwnumberAdjustments PJM applies to scheduled capacity, MW.e.g. 0
total_scheduled_capacity_mwnumberInternal scheduled capacity plus net tie flow plus adjustments, MW.e.g. 115300
operating_reserve_mwnumberTotal scheduled capacity less the load forecast, MW.e.g. 22960
unscheduled_steam_capacity_mwnumberSteam capacity available but not scheduled, MW.e.g. 14100
source_published_at_utcrequiredtimestampWhen PJM evaluated this forecast, UTC — the vintage. Every publication is kept, so one interval carries a row per vintage that covered it.e.g. 2026-09-10T02:15:00Z
collected_at_utcrequiredtimestampWhen Dryos collected this row, UTC. Stamped by the platform, not the collector.e.g. 2026-09-09T12:35:12Z

Read it

Public, read-only, no key and no sign-up. Relative times stay relative, so a URL keeps working.

The newest rows

shell
curl "https://api.dryos.ai/v1/datasets/pjm-ops-peak-rto/query?limit=12"

The catalogue entry — every column, its type and the source

shell
curl "https://api.dryos.ai/v1/datasets/pjm-ops-peak-rto"

Full parameters — bucketing, aggregation, filters and search — are on the API reference.

Ask an agent

The same stream through the Model Context Protocol, so Claude, ChatGPT, Cursor or any MCP client can query it directly.

shell
claude mcp add --transport http dryos https://api.dryos.ai/mcp

Then ask:

Show me Peak load forecast on PJM operations summary, projected RTO peak over the last 24 hours.

Setup for every client is on the MCP server page.

Changes to this collector

A change in the collector is a change in the data. Anyone reading a step in a series is owed the day it moved under them.

  1. 2026-11-15

    First collected, from PJM Data Miner 2.

    PJM's morning Operations Summary, kept by PJM indefinitely. Reconciled against live responses on 2026-11-15.

How this stream is checked

  • Pulled straight from PJM Data Miner 2 · ops_sum_frcst_peak_rto — no reseller in between — and compared against that file before it is served.
  • Null means the source did not report it — never zero.
  • A reading lands daily, each morning; the interval timestamp is the start of the interval, in UTC.
  • PJM's Eastern Prevailing Time observes daylight saving; its rows carry UTC as well. Every timestamp Dryos serves is UTC.

Related streams