Day-Ahead Transmission Constraints

The transmission constraints that bound in PJM's day-ahead market: the monitored facility, the contingency facility, the duration, and the congestion event.

Congestion & Constraints data PJM market

Query with the agent

Native record

monitored facility-contingency pair x day-ahead delivery interval

daily (day-ahead) publication cadence

Evidence

Cleared day-ahead market

A market outcome, not a physical observation

Time basis

Point-in-time records

UTC · event_time

Overview

It names which elements are expected to limit flows for the next operating day. What it does not carry is what the constraint COST: the marginal value is published separately, in pjm_da_marginal_value. For real-time binding constraints, see pjm_transmission_limits (the live tip, ~9 minutes behind) and pjm_rt_marginal_value (the settled record, ~20 hours behind). Source: PJM Market Data.

Query contract

Preserve one canonical row per (event_time, monitored_facility, contingency_facility) before aggregating.

Analysis rules

Group only after preserving the declared grain: event_time, monitored_facility, contingency_facility.

Interpretation

This identifies day-ahead constraints, not real-time binding facilities or shadow prices.

Access

Query from your own tools

Use the guarded HTTP endpoint directly, or connect an MCP client and load the dataset contract with describe_data before calling query_data.

PJM MCP API reference

HTTP endpoint

POST /api/v1/datasets/pjm_da_transconstraints/query

Need the full history of this dataset in Snowflake, Databricks or your own storage? Data services delivers it on a schedule.

Schema6

Column

Type

event_timeDateTime64(6, 'UTC')

monitored_facilityLowCardinality(String)

contingency_facilityLowCardinality(String)

durationNullable(String)

day_ahead_congestion_eventNullable(String)

ingested_atDateTime64(6, 'UTC')

Sample data

event_time	monitored_facility	contingency_facility	duration	day_ahead_congestion_event	ingested_at
2026-10-14 03:00:00.000000	LENOX-MACNEW_T LEN-MAC A 115 KV	L230.ETowanda-Hillside.2002 [NYISO]	1	LENOX-MACNEW_T LEN-MAC A 115 KV	2026-10-12 20:18:29.075663
2026-10-14 03:00:00.000000	LENOX-MACNEW_T LEN-MAC A 115 KV	L230.ETowanda-Hillside.2002 [NYISO]	1	LENOX-MACNEW_T LEN-MAC A 115 KV	2026-10-12 19:18:29.469585
2026-10-14 02:00:00.000000	ALLDAM6_138KVALL-KIT_1_LN	L345.Armstrong-HomerCity	1	ALLDAM6_138KVALL-KIT_1_LN	2026-10-12 20:18:29.075663
2026-10-14 02:00:00.000000	ALLDAM6_138KVALL-KIT_1_LN	L345.Armstrong-HomerCity	1	ALLDAM6_138KVALL-KIT_1_LN	2026-10-12 19:18:29.469585
2026-10-14 01:00:00.000000	NSALISBU_69KVNSA-PEM_1_LN	230/138.PineyGrove.AT20	3	NSALISBU_69KVNSA-PEM_1_LN	2026-10-12 20:18:29.075663
2026-10-14 01:00:00.000000	ETOWANDA-HILLSIDE 2002 TIE B 230 KV	L500.Shickshinny-Susquehanna.5067	3	ETOWANDA-HILLSIDE 2002 TIE B 230 KV	2026-10-12 20:18:29.075663
2026-10-14 01:00:00.000000	EDWSFERY_230KV23111_1_LN	L500.Doubs-GooseCreek.514	3	EDWSFERY_230KV23111_1_LN	2026-10-12 20:18:29.075663
2026-10-14 01:00:00.000000	NSALISBU_69KVNSA-PEM_1_LN	230/138.PineyGrove.AT20	3	NSALISBU_69KVNSA-PEM_1_LN	2026-10-12 19:18:29.469585
2026-10-14 01:00:00.000000	ETOWANDA-HILLSIDE 2002 TIE B 230 KV	L500.Shickshinny-Susquehanna.5067	3	ETOWANDA-HILLSIDE 2002 TIE B 230 KV	2026-10-12 19:18:29.469585
2026-10-14 01:00:00.000000	EDWSFERY_230KV23111_1_LN	L500.Doubs-GooseCreek.514	3	EDWSFERY_230KV23111_1_LN	2026-10-12 19:18:29.469585
2026-10-14 00:00:00.000000	MARDELA_69KVMAR-VIE_1_LN	230/138.PineyGrove.AT20	2	MARDELA_69KVMAR-VIE_1_LN	2026-10-12 20:18:29.075663
2026-10-14 00:00:00.000000	KINGSCRK_69KVKIN-WOR_1_LN	ACTUAL	1	KINGSCRK_69KVKIN-WOR_1_LN	2026-10-12 20:18:29.075663
2026-10-14 00:00:00.000000	ELIMSPOR_230KVELI-SUN_1_LN	L230.Montour-Saegers.2	4	ELIMSPOR_230KVELI-SUN_1_LN	2026-10-12 20:18:29.075663
2026-10-14 00:00:00.000000	MARDELA_69KVMAR-VIE_1_LN	230/138.PineyGrove.AT20	2	MARDELA_69KVMAR-VIE_1_LN	2026-10-12 19:18:29.469585
2026-10-14 00:00:00.000000	KINGSCRK_69KVKIN-WOR_1_LN	ACTUAL	1	KINGSCRK_69KVKIN-WOR_1_LN	2026-10-12 19:18:29.469585
2026-10-14 00:00:00.000000	ELIMSPOR_230KVELI-SUN_1_LN	L230.Montour-Saegers.2	4	ELIMSPOR_230KVELI-SUN_1_LN	2026-10-12 19:18:29.469585
2026-10-13 23:00:00.000000	NOTTINGH_NOT2301-3_1_LN	L500.Conastone-PeachBottom.5012	5	NOTTINGH_NOT2301-3_1_LN	2026-10-12 20:18:29.075663
2026-10-13 23:00:00.000000	EDWSFERY_230KV23111_1_LN	L500.Doubs-GooseCreek.514	1	EDWSFERY_230KV23111_1_LN	2026-10-12 20:18:29.075663
2026-10-13 23:00:00.000000	NOTTINGH_NOT2301-3_1_LN	L500.Conastone-PeachBottom.5012	5	NOTTINGH_NOT2301-3_1_LN	2026-10-12 19:18:29.469585
2026-10-13 23:00:00.000000	EDWSFERY_230KV23111_1_LN	L500.Doubs-GooseCreek.514	1	EDWSFERY_230KV23111_1_LN	2026-10-12 19:18:29.469585
2026-10-13 22:00:00.000000	NSALISBU_69KVNSA-PEM_1_LN	230/138.PineyGrove.AT20	1	NSALISBU_69KVNSA-PEM_1_LN	2026-10-12 20:18:29.075663
2026-10-13 22:00:00.000000	DEXTER_138KVDEX-MEG1_1_LN	L345.OhioCentral-MuskingumRiver	3	DEXTER_138KVDEX-MEG1_1_LN	2026-10-12 20:18:29.075663
2026-10-13 22:00:00.000000	NSALISBU_69KVNSA-PEM_1_LN	230/138.PineyGrove.AT20	1	NSALISBU_69KVNSA-PEM_1_LN	2026-10-12 19:18:29.469585
2026-10-13 22:00:00.000000	DEXTER_138KVDEX-MEG1_1_LN	L345.OhioCentral-MuskingumRiver	3	DEXTER_138KVDEX-MEG1_1_LN	2026-10-12 19:18:29.469585
2026-10-13 21:00:00.000000	KILMER_230KVKIL-SAYI_1_LN	L230.Sayreville-Kilmer-LakeNelson.W-1037	1	KILMER_230KVKIL-SAYI_1_LN	2026-10-12 20:18:29.075663

Coverage

100.0% complete0 gap days6,131 days with data

Show coverage history

Coverage: 100.0%Days with data: 6,131Gaps: 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

gaplessmore

Related congestion & constraints data

Related congestion & constraints data
Dataset	Description
Constraint Shift Factor RunsPJM · nightly (one row per completed run)	One row per COMPLETED nightly estimation of PJM constraint shift factors, and the only record that a run finished. Resolve the latest usable run here — computed_at = (SELECT max(computed_at) FROM atg.pjm_constraint_sensitivity_runs) — and never off max(computed_at) of the sensitivities themselves, because a run writes its rows in blocks that all carry the new timestamp and an unfinished or abandoned run would otherwise look like the newest one. Each row also carries how much evidence that run had: interval_coverage is the fraction of published dispatch intervals that survived admission, intervals_refused_unexplained counts intervals showing congestion with no constraint recorded as binding (an unobserved binding set), constraint_feed_lag_minutes is how far the constraint feed trailed the price feed, and constraints_seen / constraints_in_fit / constraints_reported show how many constraints bound, how many were good enough to control for, and how many earned a published estimate.
Constraint Shift Factors (Estimated)PJM · nightly (60-day rolling estimation window)	Estimated sensitivity of every PJM pricing location's price to every binding transmission constraint: one row per constraint, contingency, and location, recomputed nightly over a rolling 60-day window. This is what answers 'which nodes drive this constraint' and 'which constraints is this node exposed to'. THE DAY-AHEAD MARKET, not real time: this estimate is fitted to day-ahead marginal values against day-ahead nodal congestion and it describes day-ahead congestion. It covers PJM's day-ahead binding constraints with their contingency over roughly 14,450 pricing nodes. PJM names no terminals, so from_station and to_station are always empty. PJM's real-time shadow prices ARE ingested now (pjm_rt_marginal_value, pjm_transmission_limits) but no estimate has been fitted to them and no atg.pjm_constraints_rt canonical table exists yet — a real-time PJM answer needs that fitting work, not a new ingest. shift_factor is in the ISO's orientation — POSITIVE means an incremental MW injected at that node increases loading on the constraint and the node is paid below system lambda while it binds; NEGATIVE means generation there relieves the constraint and earns a premium. These are ESTIMATES recovered from the price identity LMP = energy - sum(shift_factor x shadow_price), not a published PTDF matrix. They are measured RELATIVE TO THE MARKET'S REFERENCE — the identity yields SF(node) - SF(reference), so a single absolute value should be quoted as 'relative to the system reference' rather than as the node's PTDF, while DIFFERENCES between nodes are exact because the reference term cancels. Three further differences from a published matrix: they describe a NODE (a generator at that node inherits its location's value, and two units at one node are indistinguishable), they reflect the topology actually in effect across the window including outages rather than a stated base case, and every one carries a std_error from a 200-draw block bootstrap that resamples whole days. Read std_error before quoting shift_factor: an estimate whose absolute value is not at least twice its standard error is not distinguishable from zero. estimation_status says why a row has no number — 'thin_support' (in the fit, so it is controlled for, but under 12 binding intervals or under 3 distinct binding days), 'no_support' (under 3 binding intervals; not a regressor), or 'collinear' (it bound in lockstep with another constraint, so the two cannot be separated). Where from_station and to_station are populated they identify the monitored element and are NOT the constrained direction — the sign of shift_factor is what says which way. Every read must pin computed_at to one run, and must resolve that run through the companion atg.<iso>_constraint_sensitivity_runs ledger rather than off max(computed_at) here — rows are written in blocks that all carry the new timestamp, so an unfinished or abandoned run would otherwise look like the newest. Mixing runs averages a node across different network topologies.
Day-Ahead Constraint Marginal ValuesPJM · hourly (day-ahead)	What each binding day-ahead transmission constraint cost in PJM, hour by hour: the monitored facility, the contingency facility, and the constraint's marginal value — its shadow price, the saving from one more MW of headroom. This is the table that says how hard a constraint bound, where pjm_da_transconstraints says only that it did. PJM PUBLISHES THIS VALUE AS A NEGATIVE NUMBER: 2,654,985 negative rows against 43 positive over the table's full history, which reaches back to 2010. Read its magnitude as the cost of the constraint and do not compare its sign against another market's. This answers day-ahead congestion only; for real-time, see pjm_transmission_limits and pjm_rt_marginal_value. Source: PJM Market Data.
PJM Day-Ahead Binding ConstraintsPJM · hourly	Which transmission facilities bound in PJM's day-ahead market and what each one cost, one row per interval and constraint. 2.65M rows, 2010-01 to the next delivery day. Columns: event_time, constraint_name, shadow_price_usd_mwh, plus contingency. The shadow price is the marginal cost of the binding limit — what the market would have saved from one more megawatt of capability on that element. This is the table that answers WHY congestion appeared; a price spread between two locations shows that they separated but not which facility separated them.